New to cmake but so far I love it.
First question I have is whether CMake is 32-bits/64-bits aware and
whether there is a way to set up a project to compile as either native
only, 32-bits only, 64-bits only or both.
So far I am unable to find anything of that nature in its built-in
configuration
Tristan Carel wrote:
The synopsis of `SWIG_LINK_LIBRARIES' macro is:
SWIG_LINK_LIBRARIES(module_name library [library...])
So try this:
SWIG_LINK_LIBRARIES(glm ${PYTHON_LIBRARIES} glm )
Whoops, that was a typo in the email on my part. I am specifying the
target name as the first argument.
Th
Bill Hoffman wrote:
> Actually, it is not stored in the solution file. It is stored in the
> .ncb file. This is a binary file, that we do not know the format of.
Ah... I see, but...
If I am not mistaken, the MS IDE *has* to select some configuration as
the default when a project is loaded. I wou
gga wrote:
Bill Hoffman wrote:
With MS IDE, there is no way for
us to change the default build type in one of the files we can
generate.
Hmm... That's probably not right. Not sure about X code, but the MSVC
IDE most definitively saves out what's the default build whenever you
create
Bill Hoffman wrote:
> With MS IDE, there is no way for
> us to change the default build type in one of the files we can
> generate.
Hmm... That's probably not right. Not sure about X code, but the MSVC
IDE most definitively saves out what's the default build whenever you
create a project from t
On 12/13/06, Abe Stephens <[EMAIL PROTECTED]> wrote:
Hi,
This might be a pretty easy question. I'm porting some code from my
usual linux/osx development environment to WindowXP. I have a library
called "glm" which builds lib/glm.dll. That appears to work.
If I try to use that library in a SWIG
Here's a handy usability improvement we recently implemented. It may
be possible to fold this type of functionality back into FIND_PATH.
The use case is this:
- CMake is called
- FIND_PATH is used to determine the location of a package
- FIND_PATH set's a variable, and places it into the cache
-
Hi,
This might be a pretty easy question. I'm porting some code from my
usual linux/osx development environment to WindowXP. I have a library
called "glm" which builds lib/glm.dll. That appears to work.
If I try to use that library in a SWIG_LINK_LIBRARIES directive, I get
an error that "gl
Sean McBride wrote:
On 2006-12-13 18:27, Axel Roebel said:
Everything works fine for unix makefiles (on Linux and Mac OS X)
Now, we tried the Xcode generator and we am having
some minor problems with it.
1)
It appears that the default build style in the Xcode project is
set to debug whil
On 2006-12-13 18:27, Axel Roebel said:
>Everything works fine for unix makefiles (on Linux and Mac OS X)
>
>Now, we tried the Xcode generator and we am having
>some minor problems with it.
>
>1)
>It appears that the default build style in the Xcode project is
>set to debug while for my makefile bu
Hi
we are working on a release for our SDIF library
(http://sourceforge.net/projects/sdif)
which should for the first time use cmake instead of
autotools as its configuration system.
Everything works fine for unix makefiles (on Linux and Mac OS X)
Now, we tried the Xcode generator and we am hav
Weiguang Guan wrote:
Hello all,
With the help from Bill Hoffman, the problem has been solved. I'd like
to share the solution with you.
You may already find articles on the net, talking about free
command-line c++ complier from within microsoft's .Net Framework SDK and
win32 libs from within
Hello all,
With the help from Bill Hoffman, the problem has been solved. I'd like to
share the solution with you.
You may already find articles on the net, talking about free command-line
c++ complier from within microsoft's .Net Framework SDK and win32 libs
from within Platform SDK. I insta
Is there a macro or command that would shorten the process
of incorporating 3rd party packages in my project? For example,
I find myself doing this in various projects:
ADD_LIBRARY(MyLib)
FIND_PACKAGE(foo)
IF(foo_FOUND)
INCLUDE_DIRECTORIES(${foo_INCLUDE_DIRS})
LINK_DIRECT
Hi,
I've noticed that when I pass a directory through LINK_DIRECTORIES
after ADD_LIBRARY, the directory is not added to the library search path.
However, INCLUDE_DIRECTORIES does not suffer such problem. This causes
a problem when I try to use Boost package. For example:
ADD_LIB
On Wednesday 13 December 2006 16:47, Alan W. Irwin wrote:
> On 2006-12-13 10:29+0100 Axel Roebel wrote:
> > Dear CMakers
> >
> > I run into a little problem with the command line flag -D.
> > I'll often use the command line flag -D to pass variables to cmake.
> > Because typing long names like
> >
On 2006-12-13 10:29+0100 Axel Roebel wrote:
Dear CMakers
I run into a little problem with the command line flag -D.
I'll often use the command line flag -D to pass variables to cmake.
Because typing long names like
-DTT_EXECUTABLE:PATH=tt
is boring I was pretty happy to see that I could do
-
Dear CMakers
I run into a little problem with the command line flag -D.
I'll often use the command line flag -D to pass variables to cmake.
Because typing long names like
-DTT_EXECUTABLE:PATH=tt
is boring I was pretty happy to see that I could do
-DTT_EXECUTABLE=tt
as well. Before you start s
18 matches
Mail list logo
