Phil Smith wrote:
C:\Program Files\GnuWin32\bin>make --version
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built
Until now only the makefile-based generators have been tested for
cross
compiling. XCode probably doesn't work. I have no idea how hard it
would be
to support cross compiling with XCode.
Ok. I've tried to find some information about supporting cross
compilation w/ Xcode, but it's far from
On Friday 25 July 2008, Emmanuel Blot wrote:
> Hi,
>
> Is it possible to use the Xcode generator to produce Xcode projects
> for cross-compilation?
> It seems that in such a case, CMake ignores the cross-compiler (gcc
> 4.x), which in turn make Xcode use the native GCC compiler.
Until now only the
Hi,
Is it possible to use the Xcode generator to produce Xcode projects
for cross-compilation?
It seems that in such a case, CMake ignores the cross-compiler (gcc
4.x), which in turn make Xcode use the native GCC compiler.
Thanks,
Manu
___
CMake
On Thursday 24 July 2008, Robert Haines wrote:
> On 18 Jul 2008, at 18:40, Bill Hoffman wrote:
...
> > However, it is not that easy to implement, since the basic type in
> > CMake is a string. There is no way to constrain the value of a
> > variable, or even store more information about a variable
C:\Program Files\GnuWin32\bin>make --version
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for i386-pc-mingw32
Mathieu Malaterre wrote:
Hi,
I have an annoying cycling dependency that appear when I use cmake
2.4.8 on debian etch but not on cmake 2.4.5 on debian stable. I'd like
to know what is the way to track it down ?
Thanks
Hi!
I don't know if this is going to help you or not but there is the
On 18 Jul 2008, at 18:40, Bill Hoffman wrote:
Alexander Neundorf wrote:
On Friday 18 July 2008, Michael Wild wrote:
On 18Jul, 2008, at 12:27, Robert Haines wrote:
I would like to point at my feature wish:
http://www.vtk.org/Bug/view.php?id=7313
Opinions?
I was looking for this functionality
Sebastian Krause schrieb:
Andreas Pakulat <[EMAIL PROTECTED]> wrote:
Thats not going to work on all platforms. There are various platforms
which don't allow static libs to be linked into shared libs.
But it should be possible to gather the sources in the subdirs into a
variable that the parent
Sebastian Krause wrote:
Andreas Pakulat <[EMAIL PROTECTED]> wrote:
Thats not going to work on all platforms. There are various platforms
which don't allow static libs to be linked into shared libs.
But it should be possible to gather the sources in the subdirs into a
variable that the parent cm
Andreas Pakulat <[EMAIL PROTECTED]> wrote:
> Thats not going to work on all platforms. There are various platforms
> which don't allow static libs to be linked into shared libs.
>
> But it should be possible to gather the sources in the subdirs into a
> variable that the parent cmake-file knows and
On 24.07.08 17:42:40, Sebastian Krause wrote:
> I have a library where the files are spread over several
> directories, but in the end have to be linked all together into a
> single library:
>
> ,
> | In src:
> |a.cpp b.cpp c.cpp
> | In src/foo:
> |k.cpp l.cpp m.cpp
> | in src/bar:
> |
Hello,
I have a library where the files are spread over several
directories, but in the end have to be linked all together into a
single library:
,
| In src:
|a.cpp b.cpp c.cpp
| In src/foo:
|k.cpp l.cpp m.cpp
| in src/bar:
|x.cpp y.cpp z.cpp
`
The easiest way to apporach thi
Hello,
for the first time I used
TRY_COMPILE(STD_BOOL TryDir TestFile.c)
in the CMakeLists-File
This results in the error-message:
"The source directory "TryDir/CMakeFiles/CMakeTmp" does not exist"
The "book" says nothing about special locations for test-files and
creating these files in the sou
At 7/24/2008 08:26 AM, Hendrik Sattler wrote:
Zitat von David Boosalis <[EMAIL PROTECTED]>:
The one complaint I have with building in another directory is when
working with emacs. I like to do my make inside of emacs, that way
when there is a compile error message I can click on it from emacs
Zitat von David Boosalis <[EMAIL PROTECTED]>:
The one complaint I have with building in another directory is when
working with emacs. I like to do my make inside of emacs, that way
when there is a compile error message I can click on it from emacs
and it takes me right to the offendin
On Wednesday 23 July 2008 21:45:34 Shead, Timothy wrote:
> On 7/23/08 1:45 PM, "Bill Hoffman" <[EMAIL PROTECTED]> wrote:
> While I'm at it, is there a good way to install an external shared library
> that handles its' symlinks? I've been doing the following, which is
> less-than-satisfying:
I've g
On 23.07.08 20:44:15, David Boosalis wrote:
>
> The one complaint I have with building in another directory is when working
> with emacs. I like to do my make inside of emacs, that way when there is a
> compile error message I can click on it from emacs and it takes me right to
> the offending
18 matches
Mail list logo
