Philip Lowman wrote:
On Fri, Dec 12, 2008 at 9:34 AM, Martin Apel martin.a...@simpack.de
mailto:martin.a...@simpack.de wrote:
Philip Lowman wrote:
On Wed, Dec 10, 2008 at 4:04 AM, Martin Apel
martin.a...@simpack.de mailto:martin.a...@simpack.de
Hi,
I try to figure out cmake parallel build capabilities.
As far as I see, multiple files in a directory can be processed in
parallel, but multiple subdirectories of a single cmake project are
still processed one after the other.
Can someone confirm this behaviour? Or can I do better?
Hi,
I have not been able to define a library dependency in a directory
different from the one in which the library target is created.
Is this done by design, or is there any way to do it?
My goal would be to have
- each library in it's own directory (and a CMakeLists.txt file
Hi,
Is there a way to define a library target, on which I could use
target_link_libraries(), without creating/building this library, i.e.
without defining it with add_library(), but with add_custom_target for
instance ?
The goal is to work on a small part of a large project: I'd like to
Hi, I'd just like to add that in order to use FindBoost in a recent
Gentoo boost installation I had to add the following library patterns to
be searched for:
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_MULTITHREADED}-${Boost_LIB_VERSION}
On 12.01.09 11:27:28, Alexandre Feblot wrote:
Hi,
I have not been able to define a library dependency in a directory
different from the one in which the library target is created.
Is this done by design, or is there any way to do it?
My goal would be to have
- each
On 12.01.09 11:27:29, Alexandre Feblot wrote:
Is there a way to define a library target, on which I could use
target_link_libraries(), without creating/building this library, i.e.
without defining it with add_library(), but with add_custom_target for
instance ?
In CMake 2.6 you can export and
Hi there,
I'd like to use cpack capabilities to compress an arbitrary
directory. From cmake -E interface I can generate gzip tarball, but
I'd rather generate a zip file (don't ask). Has anyone figure out what
is the proper command line to do that ?
cpack -G ZIP ...
Thanks,
--
Mathieu
Hi,
is there a possibility to change the type of a file from a
CMakeLists.txt file for Xcode? What I want to do is compiling a simple
c++ file as objective-c++ instead of c++. As default mode, Xcode chooses
the file extension to figure out what type the file is, but I want to
avoid changing
Ugh!
I'm using exactly the same (cmake 2.6.2, linux, unix makefiles), and run
them with gmake 3.79.1.
I also had this behaviour on Solaris 10 with dmake 7.7 (my solaris gmake
3.75 seems not to handle cmake makefiles in parallel at all).
I had a try on AIX:
- gmake 3.71 seems not to handle
Hi Andreas,
In fact, this is already what I did:
Here is a synopsis of my CMakeLists files:
ROOT CMakeLists.txt:
-define some general stuff, options, macros.
-call add_subdirectory() for all subdirectories
-*trying* to set link dependencies with
Really, the target_link_libraries command for a given lib or exe belongs in
the same CMakeLists.txt file that you call add_library or add_executable
from. What is your reason for wanting to put the list of dependencies
somewhere else?
On Mon, Jan 12, 2009 at 9:29 AM, Alexandre Feblot
On 12. Jan, 2009, at 15:12, Clemens Arth wrote:
Hi,
is there a possibility to change the type of a file from a
CMakeLists.txt file for Xcode? What I want to do is compiling a
simple c++ file as objective-c++ instead of c++. As default mode,
Xcode chooses the file extension to figure out
My question is related to my post Working with repositories:
I want to compile just a part of the project (a few libs and a few
binaries), but when linking binaries, I still need all dependency
informations. I want to get missing libs from a reference build shared
somewhere else.
Hello
I have two directories. In the first directory I have static library which I
want to use in my projects.
In the second directory is my main project which links to the static library.
How to add the static library
to the main project cmakelists so when the static library is rebuilt and
Alexandre Feblot wrote:
Ugh!
I'm using exactly the same (cmake 2.6.2, linux, unix makefiles), and run
them with gmake 3.79.1.
I also had this behaviour on Solaris 10 with dmake 7.7 (my solaris gmake
3.75 seems not to handle cmake makefiles in parallel at all).
I had a try on AIX:
-
So, I downloaded and recompiled the latest gmake (3.81).
I works much better indeed.
I should have remembered: never work with obsolete tools...
By the way, what about parallel builds with nmake makefiles ?
Thanks,
-Original Message-
From: Bill Hoffman
Hi Michael,
thanks for the fast reply. I'll test that tomorrow.
Regards
Clemens
Michael Wild schrieb:
On 12. Jan, 2009, at 15:12, Clemens Arth wrote:
Hi,
is there a possibility to change the type of a file from a
CMakeLists.txt file for Xcode? What I want to do is compiling a
simple c++
Alexandre Feblot wrote:
So, I downloaded and recompiled the latest gmake (3.81).
I works much better indeed.
I should have remembered: never work with obsolete tools...
By the way, what about parallel builds with nmake makefiles ?
I use cl with gmake.
You have to use a patched gmake.
On Mon, 12 Jan 09 16:15, Andrew Maclean wrote:
Reading on further:
The Windows API has many functions that also have Unicode versions to
permit an extended-length path for a maximum total path length of
32,767 characters. This type of path is composed of components
separated by backslashes,
So when I have a project that builds a library (call it libprovides) and I
have another project that uses that library (libuses), CMake creates a build
dependency between the two projects. I can see them when I open the Project
Dependencies dialog and notice that there are check marks next to the
On Mon, Jan 12, 2009 at 3:27 PM, James Bigler jamesbig...@gmail.com wrote:
So when I have a project that builds a library (call it libprovides) and I
have another project that uses that library (libuses), CMake creates a build
dependency between the two projects. I can see them when I open the
My goal would be to have
- each library in it's own directory (and a CMakeLists.txt
file
with a add_library command)
- all dependencies stored in a single file at the root level
root dependency file example:
target_link_libraries(mylib1 mylib2 mylib4)
The issue I'm seeing, is that if libprovides library project fails
to build, VS decides to try and build the libuses library anyway,
and then complains that libprovides isn't there.
Is this the intended behavior of VS, or did I perhaps set something
up wrong in my CMakeLists.txt?
This
Hello,
What is the origin of the current FindMPI.cmake module? I am not very happy
with this module and I don't even fully understand why is was written the way
that it is.
Specific issues that I have are:
1) It does not really take advantage of MPI compiler wrappers like it should.
The
On Mon, Jan 12, 2009 at 13:02, Bartlett, Roscoe A raba...@sandia.gov wrote:
Does anyone else have similar frustrations with FindMPI.cmake and would like
to see a new implementation as described above? How many CMake projects
have a serious MPI component that use FindMPI.cmake?
I make do with
On Mon, Jan 12, 2009 at 2:45 PM, david.k...@l-3com.com wrote:
The issue I'm seeing, is that if libprovides library project fails
to build, VS decides to try and build the libuses library anyway,
and then complains that libprovides isn't there.
Is this the intended behavior of VS, or did
27 matches
Mail list logo
