What I was trying to do earlier was specifying too much on the command
line. Combined with confusion about what "/PATH/TO/HUGIN/SOURCES" meant.
I interpreted it to mean it needed to point to the /src directory, when
it really means the parent directory of /src.
Sometimes I find compilation instructions too complex for their own
good. I know, they have to be general enough to cover a lot of
situations, but sometimes I think they're too general, trying to cover
too many possible situations. ;)
Or they're too specific. I use Debian, not Ubuntu/Fedora/Redhat, so
detailed instructions on how to do it under those other distros don't
necessarily help. ;)
Either way, it beats the days when I had to use alien to convert an RPM
to a DEB because developers only developed for Redhat.
On make install vs make package then install, when I compiled in January
2022, I used the make package option and installed the resulting
package. This time I decided not to make the package. No particular
reason, just what I did this time.
I can see one benefit to making a package and keeping it around. If I
needed to uninstall and reinstall, being able to re-install using the
package would be faster. So I went back just now and made a package to
keep around just in case.
Thanks for the help and advice!
On 10/6/22 04:26, [email protected] wrote:
How is what finally worked different from what earlier didn't work?
For example, the instructions had /PATH/TO/HUGIN/SOURCES where your
final working version had ..
I assume.. is the path to hugin sources (from the place where you had
your build directory).
It is starting to sound like there was a problem in that aspect originally.
I personally would not make the build directory of a complicated open
source project be a sub directory of the repository (except in projects
with brain dead build tools giving you no choice).
As you discovered, that method does work. But it still is not a great idea.
On Wednesday, October 5, 2022 at 11:25:49 PM UTC-4 GnomeNomad wrote:
On 10/5/22 02:02, Kornel Benko wrote:
> Am Tue, 4 Oct 2022 21:54:17 -1000
> schrieb "David W. Jones" <[email protected]>:
>
>> On 10/4/22 20:40, Gunter Königsmann wrote:
>>> Either you haven't gettext installed
>>
>> I have gettext 0.21-4 installed.
>>
>>> or your cake is too old to know about it.
>>
>> Cake? You mean cmake? cmake is v3.18.4.
>>
>> This is on Debian 11. It's been almost a year since the last time I
>> compiled Hugin. I successfully compiled Hugin 2021 to a /usr/local
>> installation 1 January 2022.
>>
>> Ideas?
>>
>
> It is part of hugin sources. Don't know, why cmake is not finding
it.
>
> Look foe 'CMakeModules/FindMSGFMT.cmake' in your cloned hugin.
>
> Kornel
I find that one in the cloned hugin tree. Cmake is still not finding
MSGFMT, although that is installed.
Here's what cmake tells me:
CMake Error at celeste/CMakeLists.txt:71 (set_target_properties):
set_target_properties called with incorrect number of arguments.
CMake Error at translations/CMakeLists.txt:7 (find_package):
By not providing "FindMSGFMT.cmake" in CMAKE_MODULE_PATH this
project has
asked CMake to find a package configuration file provided by
"MSGFMT", but
CMake did not find one.
Could not find a package configuration file provided by "MSGFMT"
with any
of the following names:
MSGFMTConfig.cmake
msgfmt-config.cmake
Add the installation prefix of "MSGFMT" to CMAKE_PREFIX_PATH or set
"MSGFMT_DIR" to a directory containing one of the above files. If
"MSGFMT"
provides a separate development package or SDK, be sure it has been
installed.
Gettext and msgfmt are installed here.
Anyway, here's what finally worked:
1. Run "cmake .." in the build directory. That put the missing MSGFMT
.cmake files in a subfolder under the build directory.
2. Run "make".
3. Run "sudo make install".
That gave me a Hugin reporting itself as "Version: Pre-Release
2021.1.0.33b93e37f209". Is that correct?
--
David W. Jones
[email protected]
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/92dffeec-1b31-3377-e179-4e18da861f9b%40gmail.com.
