Luigi Calori wrote:
for this assembly, cvs.exe, tar, gzip and similar stuff are required,
they are usually available under Linux but not under windows, so I had
to collect them...
cmake -E tar [options] can create a tarball for you. Easier than
worrying about where the hell a tar or gzip
I' ve done some work on CMake and OSG:
the approach for OpenThreads and Producer has been to build them in the
same build for OSG settin output dll in the same dir,
WITHOUT installation.
I configure also .bat or .sh script to set up the environment on the fly
, for example to run examples, mimi
But that's OSG. Says nothing about OpenThreads and Producer. I'm
saying, write a CMake script that installs OpenThreads and Producer in a
way they're expected to be installed. There's really no value in
CMakeifying a build that the library maintainers themselves aren't going
to support. All yo
E. Wing wrote:
One frequent reason people might run
without the formal *installation* is that OSG has yet to put out a
release with a stable API and ABI.
But that's OSG. Says nothing about OpenThreads and Producer. I'm
saying, write a CMake script that installs OpenThreads and Producer in a
Anyway, I would really like to improve this current Makefile scheme if
possible so it is more a one step build without the user having to
intervene with setting environment paths or 'installing'.
Is that even technically possible in the underlying build dependencies?
Yes, I believe this is te
Mike Jackson wrote:
It is probably possible as long as the directory structure is adhered
to.. that is the big thing.. Then we can just build in the paths to
the CMake files. Not the best solution, but would work.
Mike
On 8/21/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
E. Wing wrote:
It is probably possible as long as the directory structure is adhered
to.. that is the big thing.. Then we can just build in the paths to
the CMake files. Not the best solution, but would work.
Mike
On 8/21/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
E. Wing wrote:
>
> Anyway, I would r
E. Wing wrote:
Anyway, I would really like to improve this current Makefile scheme if
possible so it is more a one step build without the user having to
intervene with setting environment paths or 'installing'.
Is that even technically possible in the underlying build dependencies?
For insta
Eric,
I am in the process of writing something similar in CMake for our
own project. I have like 5 or 6 subprojects that need to be built
first. The code layout is similar to OST_OT_OP layout. I have one
CMake file in the Main directory that includes "../{other projects}
and now with one invocati
There's actually not too much going on the OSG list so don't worry
about it too much. Perhaps the surprise was the fact that QMake also
supports Xcode generation. I'm having trouble finding specifics on it
though.
As far as CMake questions go, I actually have a couple maybe you guys
can answer n
10 matches
Mail list logo
