Am Sonntag 19 September 2010 schrieb kfj: > On Sep 19, 1:05 pm, Kornel Benko <[email protected]> wrote: > > Sorry, don't know much about nsis. Except you could use > > It is 'msys'. I am not attempting to make a package, just to compile > libpano13 from source, together with it's collateral applications. > msys ('minimal system') is an environment to use the minGW tool set, > which is the GNU compilers for Windows, to make a long story short. > The difference to cygwin is that the generated executable will be > genuine Windows and not require the cygwin DLL. Check > > www.mingw.org > > If you want to find out more. The great thing about it is that you can > often take a source distribution that was made for Linux or UNIX and > run the ./configure - make - make install cycle on it, and come out > with a Windows EXE or DLL ready to run under Windows without any > auxillary software needed. I think initially libpano was meant to be > compiled with minGW, at least that is what's used in the tutorial > > http://wiki.panotools.org/Build_pano12_from_sourcecode
This one describes it for pano12 (as opposed to pano13). But OK, I did not find
anything other either.
> which I used to start out on my compilation attempt. From what I have
> gleaned so far cmake can use the minGW compilers, it's more a question
> of having a suitable CmakeLists.txt. Now I know next to nothing of
> cmake, but it seems you do.
Somehow yes, but as I do not have minGW, it is not so easy ...
> I just don't know where to start, and I
> have already invested yet another half day to wrestle with cmake - it
> seems to have a MSVC fixation when I set it onto the libpano sources I
> have here and wants to do stuff like call 'cl', and it also thinks
> itself inside the hugin source tree, which it is not.
No, it only "thinks" it needs some cmake-modules, which are in the hugin
source. It is only done to not duplicate them.
But this is not really needed.
What we need are the modules "FindTIFF.cmake", "FindJPEG.cmake",
"FindPNG.cmake" etc., which are in the cmake2.8 distribution also.
> If I run ./
> configure, it very cleverly determins every conceivable aspect of my
> system and environment. How can I use cmake to do the same thing and
> then build the targets with the GNU tools?
> Keeping compatible with minGW is very desirable, since it's free and
> Linux-compatible.
Say, your main CMakeLists.txt for a project is in "/x/source"
Normally one only creates a directory, say "/x/build"
cd /x/build
cmake /x/source
make
make install # this one as a superuser
If we were coding perfectly, then everything would be installed now.
Without creating a package, this has some disadvantages, (you have to keep
trace of installed files, in case you want to
clean your filesystem again). But this should be the same, as with configure.
> with regards
> KFJ
Kornel
--
Kornel Benko
[email protected]
signature.asc
Description: This is a digitally signed message part.
