Hi,
On Thursday 27 September 2007 16:31, Bill Hoffman wrote:
> > I think there's a way to tell CMake to either use lib or lib64,
> > something like LIB_SUFFIX.
>
> CMake does a test for sizeof void* if it is 8 bytes then lib64 is
> searched before lib in all FIND_* stuff.
That is way too croase a
Hi,
On Thursday 27 September 2007 15:53, Andreas Pakulat wrote:
> Just to state the obvious: Thats backwards compared to what distro's
> have these days. */lib is always the native libs and then you have
> either lib64 or lib32 (at least AFAIK, don't have any 64-bit system)
No.
On a redhat or sus
Hi,
Thank you all for answering. First, I would like to mention that the
pkg-config alternative isn't very portable. Like other already said, it does
not work well under Microsoft Windows nor MSVC. Also, all paths are wrote in
.pc files which aren't very portable.
I think I might have found a sol
Am Freitag 28 September 2007 schrieb Andreas Pakulat:
> On 27.09.07 16:07:46, Alan W. Irwin wrote:
> > On 2007-09-27 21:53+0200 Andreas Pakulat wrote:
> > >No it doesn't work properly on win32 - AFAIK. Thats the reason why all
> > >cmake FindXXX modules for KDE4/win32 don't use pkgconfig. I'm not s
Am Freitag 28 September 2007 schrieb Brandon Van Every:
> On 9/27/07, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
> > I'm reporting 2nd hand information from people that have long-time
> > experience with pkg-config. Unfortunately I can't find the thread on the
> > kde lists where Christian Ehrliche
On 9/27/07, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
>
> I'm reporting 2nd hand information from people that have long-time
> experience with pkg-config. Unfortunately I can't find the thread on the
> kde lists where Christian Ehrlicher pointed out the other issues with
> pkg-config, maybe I'll h
Did you run nm on the library containing these symbols to verify they exist?
_tetra_zone_copy_
_xyz_vertex_copy_
The trailing underscore is reminiscent of a Fortran compiler. Are you using
the write convention when calling these functions from C code? On Linux,
you would call the Fortran functi
On 2007-09-27 16:12-0400 Brandon Van Every wrote:
[...]There are no Windows binaries of pkg-config
available on the website. Googling around, I don't see any kind of
self-contained pkg-config.exe for use on the Windows Command Prompt.
I do see some .exe's that are part of Cygwin or MSYS toolcha
Mike Jackson wrote:
Are there actual implementations for the undefined functions? If there
are implementations, are they being skipped because of some #define?
Just some simple mistakes that I have made in the past.
The thing is the code is the same for linux and for mac, and it works
well wi
I'm having some trouble getting a clean way to set the warning level
in my projects with Visual Studio 2005.
When I try this
SET(CMAKE_C_WARNING_LEVEL 4)
SET(CMAKE_CXX_WARNING_LEVEL 4)
It seems to be ignored because the project files still have the
warning level set to 3. I only want to turn up
On 27.09.07 16:07:46, Alan W. Irwin wrote:
> On 2007-09-27 21:53+0200 Andreas Pakulat wrote:
> >No it doesn't work properly on win32 - AFAIK. Thats the reason why all
> >cmake FindXXX modules for KDE4/win32 don't use pkgconfig. I'm not sure
> >wether it was about the paths in the .pc files or somet
Are there actual implementations for the undefined functions? If
there are implementations, are they being skipped because of some
#define? Just some simple mistakes that I have made in the past.
also, is there an actual libskinmesh.a in the following location:
/Users/program/qtskinmesh/build
Josef,
I think you want to add a build type
http://www.cmake.org/Wiki/CMake_Useful_Variables see the comments under
CMAKE_BUILD_TYPE.
I've used the following to remove the extra configurations that cmake makes
by default that I didn't want in my project files.
SET( CMAKE_CONFIGURATION_TYPES "Debu
On 2007-09-27 21:53+0200 Andreas Pakulat wrote:
On 27.09.07 12:31:31, Alan W. Irwin wrote:
On 2007-09-27 20:10+0200 Hendrik Sattler wrote:
Am Donnerstag 27 September 2007 schrieb Félix C. Morency:
The use of
pkgconfig is prohibited, just like shell scripts and env. variables. The
solution ha
> > > Also, does cmake have an idea of platforms, or does it assume
Win32?
> >
> > CMake does not assume anything about Win32 or any other platform.
>
> What I mean is, in vcproj files combine the configuration and the
> platform
> labels to form a compilation target, i.e Release|Win32, Debug|x6
Mike Jackson wrote:
Marie,
Use the following in your CMakeLists.txt file, generally near the
top just after you define the PROJECT (... )
SET (LIBRARY_OUTPUT_PATH "${PROJECT_BINARY_DIR}/Bin" CACHE INTERNAL
"For libraries.")
SET (EXECUTABLE_OUTPUT_PATH "${PROJECT_BINARY_DIR}/Bin" CACHE INTER
Mike Jackson wrote:
Comments are in-line. (Note, this is one particular style of using
CMake, other variations are perfectly valid)
--Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
On Sep 27, 2007, at 2:50 PM, Marie-Christine Vallet wrote:
Hi,
I
quot; CPackConfig.cmake
then
dpkg-deb -I .deb
should show you
Architecture: your_arch
It works for me on a Debian/Etch+SID with CMake 2.5-20070927 (current CVS)
This will work, but not as useful as the way I thought it was working,
in the first place.
I think the work on CPack Generator is n
On 27.09.07 16:12:19, Brandon Van Every wrote:
> On 9/27/07, Alan W. Irwin <[EMAIL PROTECTED]> wrote:
> > On 2007-09-27 20:10+0200 Hendrik Sattler wrote:
> >
> > > Am Donnerstag 27 September 2007 schrieb Félix C. Morency:
> > >> The use of
> > >> pkgconfig is prohibited, just like shell scripts and
Marie-Christine Vallet wrote:
> Juan Sanchez wrote:
>> Could this be an issue with linker order? Most linkers are one pass.
>> The library containing the undefined references should be on the linker
>> line before the library containing the symbols, or vice-versa (I keep
>> forgetting).
>>
>>
>
Juan Sanchez wrote:
Could this be an issue with linker order? Most linkers are one pass.
The library containing the undefined references should be on the linker
line before the library containing the symbols, or vice-versa (I keep
forgetting).
The symbols are part of the newly created librar
On 9/27/07, Alan W. Irwin <[EMAIL PROTECTED]> wrote:
> On 2007-09-27 20:10+0200 Hendrik Sattler wrote:
>
> > Am Donnerstag 27 September 2007 schrieb Félix C. Morency:
> >> The use of
> >> pkgconfig is prohibited, just like shell scripts and env. variables. The
> >> solution has to be as portable as
Marie,
Use the following in your CMakeLists.txt file, generally near the
top just after you define the PROJECT (... )
SET (LIBRARY_OUTPUT_PATH "${PROJECT_BINARY_DIR}/Bin" CACHE INTERNAL
"For libraries.")
SET (EXECUTABLE_OUTPUT_PATH "${PROJECT_BINARY_DIR}/Bin" CACHE
INTERNAL "For executab
Could this be an issue with linker order? Most linkers are one pass.
The library containing the undefined references should be on the linker
line before the library containing the symbols, or vice-versa (I keep
forgetting).
Do the libraries contain the symbols that they should? Use whatever the
On 27.09.07 12:31:31, Alan W. Irwin wrote:
> On 2007-09-27 20:10+0200 Hendrik Sattler wrote:
>
> >Am Donnerstag 27 September 2007 schrieb Félix C. Morency:
> >>The use of
> >>pkgconfig is prohibited, just like shell scripts and env. variables. The
> >>solution has to be as portable as it can be (w
Mike Jackson wrote:
What are the errors you are getting on OS X?
I get an undefined symbol error for several of my variables.
If I do the linking manually, leaving out the library, and putting the
.o of the library and use the same flags, it works.
Also, at least one comment, I am not sure yo
What are the errors you are getting on OS X?
Also, at least one comment, I am not sure you want to be setting the
PROJECT_BINARY_DIR Variable?
What are you trying to do with this statement:
SET(PROJECT_BINARY_DIR
${CMAKE_SOURCE_DIR}/bin)
--
Mike Jackson Senior Research Engineer
Innovative
On 2007-09-27 20:10+0200 Hendrik Sattler wrote:
Am Donnerstag 27 September 2007 schrieb Félix C. Morency:
The use of
pkgconfig is prohibited, just like shell scripts and env. variables. The
solution has to be as portable as it can be (win32, linux, macosx, etc.)
pkgconfig _is_ portable. It wo
Richard,
This project organization is much better, Kudos. However, most of our
directories include only a single project file so there seems to be a lot of
redundant folders in this type of layout, so maybe a little additional
feature that if there is only a single project in the directory don't
Hi,
I have a project which in which I create a library and then I use
this library with my executable. The way I set it up seem to be working on
linux (fedora) but it does not work on mac ox10.
Could someone tell me what I am doing wrong,
Thanks,
Marie
Project tree
*Projectdir
**mdi
**
I've ran into similar problem.
Instead of keeping the original files as golden results, I
wanted to keep MD5 checksums of these files. There are two reasons
for it: disk space constraints and different file format
support. The generated files can take up a lot of disk space. If
a
Am Donnerstag 27 September 2007 schrieb Félix C. Morency:
> Could you please elaborate on "an automatically written cmake script". I
> would like to know more about it and how it can be acheived.
See http://www.cmake.org/HTML/Documentation.html and search for
EXPORT_LIBRARY_DEPENDENCIES.
The FILE
On 9/27/07, Dirk Colbry <[EMAIL PROTECTED]> wrote:
> 1. Why didn't the MATLAB version of gmake work? My guess is that since the
> MATLAB version of gmake is built for windows, it is having difficulty with
> the cygwin directory structure.
Not sure about this one -- your guess sounds reasonable, t
Both which and gmake commands point to the gmake file in MATLAB as the first
in my path directory. However, when I look at my PATH directory the
/usr/bin folder is first in the path list (see print outs at the end of this
message).
I check the /usr/bin directory and it does not contain the gmake
What happens if you type "gmake --help" or "which gmake" from the same
prompt...?
CMake should just use the PATH env variable to find the right gmake
first. If not there, it may look in some other well known places, but
if there is one in your PATH, it will use it...
Most likely considered a feat
I got a new XP computer at work so I installed some of my standard tools
(including cygwin and a new copy of MATLAB 2007a). When I try to compile
one of my cmake projects in cygwin, I get an new error (see end of message
for error printout). It seems that cmake is incorrectly associating an
execu
I was wondering if there is a Jamfile generator for CMake for either
Perforce Jam or Boost Jam? I'm doing build system experiments, and I'd
like to export the CMakeLists.txt contents to alternative build systems.
Thanks.
Josh
___
CMake mailing list
I am using ADD_CUSTOM_COMMAND to produce an output.
Unfortunately, if the commands in it fail, the OUTPUT. Hence the OUTPUT
is up to date, even though it is invalid. Is there a way to tell
ADD_CUSTOM_COMMAND to remove its output when it fails?
Thanks,
Juan
___
Andreas Pakulat wrote:
But cmake looks in */lib
directories where some x86 libs are present that are not present for the
x86-64 case.
The question here is even worse - which one is the native one?? lib or lib64??
And which ones should cmake accept?
I think there's a way to tell CMa
This may be common knowledge already, but I was wondering what the best
way to get cmake to build both unix make files and visual studio files
for the same project is. I'd like to use makefiles for building my
project, but I still need vcproj files so that the developers can use
visual studio for
Attached is an updated patch that works with 2.4.7.
-Richard
Sylvain Benner wrote:
Is there a way to group projects in a solution? Something like this
would be handy
CMakeProject
--> ALL_BUILD
--> ZERO_CHECK
etc
lib
--> lib1
--> lib2
Possibly something that follows
On 27.09.07 15:36:11, Mathias Froehlich wrote:
> On Thursday 27 September 2007 11:33, Dizzy wrote:
> > In your example, the native arch it's x86-64 or x86? And then you are
> > compiling for a target x86 or x86-64?
> The native arch is x86-64. And I compile for x86-64. The native archs libs
> will
Hi,
On Thursday 27 September 2007 15:21, Sanchez, Juan wrote:
> If you want to check without actually compiling. There is the file command
> which can tell you about a shared library or any other file on your
> filesystem.
>
> ~> file /opt/firefox/libfreebl3.so
> /opt/firefox/libfreebl3.so: ELF
Hi,
On Thursday 27 September 2007 11:33, Dizzy wrote:
> Also generally, FIND_LIBRARY(), FIND_FILE() (which are generally used in
> FindPackage scripts) are both configurable setting some variables for the
> paths (see the cmake man page on them).
So you can avoid that cmake will look into /lib an
Hi,
Thank you for anwsering so fast.
>> 1. What solution do you think is the best: "A main master script" that
>> knows every dependencies of every projects VS "Completly indenpendant
build
>> script" that we could simply include if we need them and their
dependencies
>> ? Please justify.
> If t
Hi all,
If I set CMAKE_OSX_ARCHITECTURES to, for example, "i386 ppc", then
configure, generate, and make, everything works great. However, if I
then go back into ccmake and append a new architecture, say change it to
"i386 ppc ppc64" then configure, generate, and make again, the make
step just p
If you want to check without actually compiling. There is the file command
which can tell you about a shared library or any other file on your filesystem.
~> file /opt/firefox/libfreebl3.so
/opt/firefox/libfreebl3.so: ELF 32-bit LSB shared object, Intel 80386, version
1 (SYSV), stripped
~> fi
> > Also, does cmake have an idea of platforms, or does it assume Win32?
> >
> > CMake does not assume anything about Win32 or any other platform.
>
> What I mean is, in vcproj files combine the configuration and the
platform
> labels to form a compilation target, i.e Release|Win32, Debug|x64.
>
On Thursday 27 September 2007 12:12:56 Mathias Froehlich wrote:
> Hi,
Hello
> I have problems with nonstandard architectures.
>
> cmakes mechanism to see if some package is installed usually just looks if
> some files are present. That is good as long as you just compile for the
> standard archit
> > > I'm looking at cmake as a potential solution to some build
problems
> > I'm having. Am I right in thinking that cmake only allows for four
> > hard-coded configuration labels, DEBUG/RELEASE/etc? Where should I
> > look to add to these, as we've got more configurations than this.
>
>
http:/
Josef Karthauser <> wrote:
> I'm looking at cmake as a potential solution to some build problems
> I'm having. Am I right in thinking that cmake only allows for four
> hard-coded configuration labels, DEBUG/RELEASE/etc? Where should I
> look to add to these, as we've got more configurations than
I'm looking at cmake as a potential solution to some build problems I'm
having. Am I right in thinking that cmake only allows for four
hard-coded configuration labels, DEBUG/RELEASE/etc? Where should I look
to add to these, as we've got more configurations than this. Also, does
cmake have an ide
Hi,
I have problems with nonstandard architectures.
cmakes mechanism to see if some package is installed usually just looks if
some files are present. That is good as long as you just compile for the
standard architecture on a specific operating system.
But if I build for some non default arc
Is there a way to group projects in a solution? Something like this
would be handy
CMakeProject
--> ALL_BUILD
--> ZERO_CHECK
etc
lib
--> lib1
--> lib2
Possibly something that follows the file system setup.
-Neal
This topic has been addressed few days ago, a quick
How do I get the INCLUDE_DIRECTORIES path? I need to feed into into the
search path for the swig command line.
Documentation taken from a "man cmake" command:
GET_DIRECTORY_PROPERTY
Get a property of the directory.
GET_DIRECTORY_PROPERTY(VAR [DIRECTORY dir] property)
Hi,
CMake searches for make program while configuring and stores its path
in CMAKE_MAKE_PROGRAM variable but I need to call it myself to build
the project. There are no problems if my PATH environment contains
make's path but in some cases it doesn't.
For example, MinGW programs are searched v
56 matches
Mail list logo
