libcvd-members
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libcvd-members] windows project file changes


From: Joseph Newman
Subject: Re: [libcvd-members] windows project file changes
Date: Mon, 27 Jul 2009 13:36:49 +0100

Hi Guys,

Probably what would be best for most windows users would be to have access to an archived version of the unix-style install that Gerhard is proposing. 

For a different project I wrote a SCons script that would not only build my project under Windows but would also package it up with all of the dependencies in such a way that would allow other users to develop against it. I may be able to do this for libcvd and create a buildbot that would keep up to date with the latest changes.

In general I have found unified build environments for cross-platform projects to have been more trouble than they are worth. In general OS X and linux are sufficiently similar that they can be handled straightforwardly, but targeting Visual Studio on Windows was too different.

Joe


On 26 Jul 2009, at 20:50, Gabriel Nützi wrote:

Why not just putting the latest JPG and Pthread lib in there as well, so we know that the libcvd works with the actual JPG and Pthread
makes it much mor comfortable, and is not a great deal ...

cheers gabriel, (from switzerland, who is using Libcvd with a modified PTAM -> IMU VISION Controller for a helicopter ) :-)


Am 23.07.2009 um 15:25 schrieb Gerhard Reitmayr:

Hi everyone,

just a quick heads-up on what I plan to do with the Windows project files. Its getting tedious to keep all the include and lib paths correct in lots of project files, so I propose to do the following:

- do a unix style install into three directories for headers, libs and bins (which include the shared libraries, dlls under windows)

- these three directories are set by the user with three environment variables:
INCLUDEDIR, LIBDIR, BINDIR . of course they can be set from a single common prefix like this:
PREFIX=something
INCLUDEDIR=%something%\include
etc.

- project files will only use a single include dir (besides the local one) and libdir

- projects will also have an install project which copies the files into the installation location defined above.

- some 3rd party libraries (like jpeg, ptheads-win32) can be copied by the user into these directories to make them available.

what do you think ? any thoughts about this ?

cheers,
Gerhard




_______________________________________________
libcvd-members mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/libcvd-members



_______________________________________________
libcvd-members mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/libcvd-members


reply via email to

[Prev in Thread] Current Thread [Next in Thread]