Re: can not find the file(enblend/INSTALLDIR )

It depends on what you're trying to accomplish.

If you're trying to compile Hugin 0.7 or enblend/enfuse for that, I can't be sure - I've never done that. You mentioned enblend 3.1 (even though 3.2 is out, and is, AFAIK, backwards compatible), so I'm assuming you are intending to do that - but I'm afraid you'll need to look further yourself for that. A simple search for enblend.exe / enfuse.exe should help you locate the proper paths, and CMake will complain if it cannot find them, which is the entire point of that step. If CMake doesn't complain, then there is no need for copying, I would wager. If CMake does complain, you can always manually direct CMake to the path of the executables.

However, if you're intending to compile Hugin 0.8 / from an SVN version more recent than 3479, you're much better off reading http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29 and following the directions there, either downloading the 32-bit SDK or compiling your own 32-bit or 64-bit version (depending on your needs). Once installed/compiled, you should be able to simply run CMake for Hugin, and the only prompts you'll receive are potentially for the SVN number, the builder name (eg: your name) and the build date.

You can pick up from Step 9 at http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK#Build_hugin if you opt the precompiled SDK route.



From: hugin-ptx@... [mailto:hugin-ptx@...] On Behalf Of ???
Sent: Sunday, July 05, 2009 10:13 PM
To: hugin-ptx@...
Subject: [hugin-ptx] Re: can not find the file(enblend/INSTALLDIR )

I use TortoiseCVS (version1.10.10) to compile hugin_enblend_sdk_msvc2008_v2 with msvs 2008.
Is that correct?

thanks, does that mean the step 6 is wrong? and what step 6 should be?
(open huginbase/enblend/enblend_msvc2008.sln with Visual Studio 2008 Express. Change the target configuration to 'release' (build menu, configuration manager). Click build solution. After it completes, copy enblend/INSTALLDIR into huginbase/enblend-3.1/. The hugin install script expects this directory.)
 

2009/7/6 Ryan Sleevi <ryan+hugin@...>

Enblend/Enfuse don't use the CMAKE-based system that Autopano-sift-c and
Hugin use.

As a result, binaries are not deployed into an INSTALLDIR location. Instead,
once compiled, they are typically located in
enblend-enfuse-3.2-dir\src\Debug and enblend-enfuse-3.2-dir\src\Release ,
where enblend-enfuse-3.2-dir is the directory where you deployed the
enblend-enfuse-3.2 sources.

Are you having trouble with the CMAKE file for Hugin locating these files,
or were they just not where you expected them to be?




--
李志远



--~--~---------~--~----~------------~-------~--~----~
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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---