Maybe there is something I originally did not understand. I'm looking more into the compile time dependency than the run time... aka I want to build enblend. I pull the source. First thing I see is that I'm missing wxwidgets, lcms, the tiff library, etc...
Does the package manager handle this? The reason I ask is that I'd like to get a dev environment setup, and help simplify the process for the next people who would like to. I think the SDK is nice as long as we have a core of people keeping it up to date which seems to be problematic now. So maybe another solution, or a hybrid solution could be done. If there is a file that contain the list of what is required (lcms, wxwidgets, boost version X, etc) that is used by the package manager, maybe there is a way to reuse that information to at least provide a checklist to the user of what is required; and the best solution would be to automate the pulling of those packages. If some of my assumptions are wrong, don't hesitate; I'm new to a lot of this. nick On Wed, Nov 11, 2009 at 3:51 AM, Stefan Peter <[email protected]>wrote: > > Nicolas Pelletier wrote: > > Hi, > > > > A little researched showed that there are now a few package managers > > that work on windows. Has this been looked into as a solution for hugin? > > I don't think that a packet management system that is not part of the > operating system is of any use. > > I think that one of the big problems is autopano-sift-c. Being > encumbered by a patent, it should not distributed with hugin. On the > other hand, hugin requires a control point generator. > > Another issue is enblend/enfuse. As long a no fine 4.0 is released, we > should 3.2 IIRC. > > So, maybe a modular installer will help? Breaking the monolithic windows > installer into sub projects (hugin-gui, hugin-tools, enblend/enfuse, > autopano-sift-c, ...) that could be maintained independently but tied > together for building the final hugin installer? But then we'd need even > more maintainers from the windows camp ... > > > > > Also, in linux, what file is used to find the required packages? I.e. > > what file contains the dependency? > > > There is no single file IIRC. And the whole process with all > dependencies is documented on > http://wiki.panotools.org/Hugin_Compiling_Windows and > http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK > > We currently have a binary for the 2009.2.0 release. What is needed is a > volunteer that repeats this for the 2009.4.0.rc2 so the process is > stable once 2009.4.0 is released. And, if there is enough time and urge, > a 2009.2.1 version that fixes some issues may be a prudent thing to do, > too. > > Regards > > Stefan Peter > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
