I'm not exactly a professor on this subject either, but from my understanding (and experience), package managers are mostly for binary releases, in other words: the runtime dependencies. I'm not aware of a package manager for build time dependencies. These are generally different from runtime dependencies, e.g. libtiff is needed to compile Hugin, but not to run it (if everything gets linked statically).
If you want to know the build time dependencies, you can look up the list at the wiki pages mentioned earlier. I'm not sure if you can *easily* extract the list from the Hugin sources (makefiles, cmake files), but it should be possible, since libraries need to be linked, and the instructions to do so need to be available. I do like your idea of automating the process of downloading and building external dependencies. In fact, it should be possible. The mingw-cross-env approach I'm figuring out in another thread [0] does this more or less, but for cross building from Linux (host) to Windows (target, for the binaries). In the .mk files you can specify the dependencies, which will be downloaded and built automatically if they don't exist already. Currently that system is targeted at libraries, not at complete programs like Hugin, but the system can already be "hacked" to work for programs too. You only have to make sure that the files which are built aren't automatically destroyed but are copied to a safe location, that's all. Or have mingw-cross-env build the dependencies and work out Hugin by yourself, which is what I'll be trying to do. If you want to build on Windows, for Windows, I cannot help you, because I haven't tried. You hinted you found some "package managers" for Windows, but didn't say which ones? Maybe others can help you with that. By the way I disagree with Lukas and Peter on having to use an external tool or package manager. Microsoft just "forgot" to include a proper solution for package management *completely*, so why not use an external tool? Microsoft didn't supply CMake either, but I don't hear anyone complaining about that... If a package manager can become an integral part of a fully automated build chain, why not? I think this would be a great thing. [0] http://groups.google.com/group/hugin-ptx/browse_thread/thread/935d140fa7dc80df/b7e74c081252a6b3#b7e74c081252a6b3 -- Bart --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
