On Wed, Dec 14, 2011 at 5:31 PM, David Cole wrote:
> This is because we should really only allow one project command per
> CMakeLists.txt file, but since we do not error out, it's difficult to change
> at this point in time...
>
> --build uses the CMAKE_PROJECT_NAME cache variable to decide what
This is because we should really only allow one project command per
CMakeLists.txt file, but since we do not error out, it's difficult to change at
this point in time...
--build uses the CMAKE_PROJECT_NAME cache variable to decide what sln file to
use, and that corresponds to the first project
I wrote a TestForPosix module for looking if the system supports a POSIX /
XPG / SUS standard and I wanted for you experts to look and criticize if
you find anything wrong. I would also ask how can I make a request for it
to be included in CMake 2.8.7, because it is (in my opinion) a very good
cont
I figured that, but that is one hell of a scary find module... I tend to
stay away from it :)
Thanks guys.
-
Robert Dailey
On Wed, Dec 14, 2011 at 5:33 PM, Tim Gallagher wrote:
> Boost takes arguments for versions of the library if you need a concrete
> example.
>
> Tim
>
> - Origi
Boost takes arguments for versions of the library if you need a concrete
example.
Tim
- Original Message -
From: "Alexander Neundorf"
To: cmake@cmake.org
Sent: Wednesday, December 14, 2011 5:11:45 PM
Subject: Re: [CMake] Find package with version numbers
On Wednesday 14 December 2011,
visual studio 2010; cmake latest
cmake .. - generates a .sln file that is comprised of the last project
in the top level.
cmake --build . - tries to build the .sln that is comprised of the
first 'project' command that is encountered in the script.
If I reverse the project and include line
On Wednesday 14 December 2011, Robert Dailey wrote:
> Is there any example of how to write a find module for find_package() that
> utilizes version numbers? How is the version number passed into the
> Find*.cmake module? The documentation on this is very confusing and
> discusses creating a version
Is there any example of how to write a find module for find_package() that
utilizes version numbers? How is the version number passed into the
Find*.cmake module? The documentation on this is very confusing and
discusses creating a version.cmake file. I looked in the CMake modules
directory for an
I am trying to add a library to implicitly link against for the Absoft Fortran
compiler. CMake generates the libraries to implicitly link against for this
compiler seemingly from source code, since the Compiler/Absoft-Fortran and
Platforum/Linux-Absoft contain nothing about what libraries to im
It looks like this find script has been written for kde:
http://old.nabble.com/Review-Request%3A-Add-a-FindQtMobility.cmake-file-td31823359.html
I don't see it included in src/cmake/Modules - any plans to include it
with CMake?
David
--
Powered by www.kitware.com
Visit other Kitware open-source
On 12/14/2011 09:43 AM, Totte Karlsson wrote:
>
> On 12/13/2011 4:15 PM, David Cole wrote:
>> RUNTIME_OUTPUT_DIRECTORY is a target property, not a variable. You'd
>> have to use get_property to retrieve its value, not
>> ${RUNTIME_OUTPUT_DIRECTORY}...
>
> Thanks! I ended up with the following, in
On 12/14/2011 11:23 AM, Alexander Broekhuis wrote:
> Hi,
>
>>
>>
>> First of all, you definitely need the library target in order to build
>> the library, and CMake ignores each file in the list of sources which
>> is not necessary for this purpose. IMO, that's quite reasonable; e.g.,
>> you would
>
>
>
> Yes now it's clear.
> You are looking for something like
> add_library like command which would produce the OSGi bundle which
> is the purpose of your "bundle" macro.
>
>
Yes this is exactly what I'd like to do, but taking Michael remarks into
account, I now think it would make more sense t
On 12/14/2011 10:55 AM, Alexander Broekhuis wrote:
> Hi,
>
> Thanks for you replies,
>
>
>>> In my case the output is the ZIP file. So the zip file is produced by the
>>> top level target, and I don't want/need a separate target for it.
>>
>> Yes but CMake's jobs is to build libraries and execut
2011/12/14 Alexander Broekhuis :
> Hi,
>
> Thanks for you replies,
>>
>> Yes but CMake's jobs is to build libraries and executables not "bundle"
>> which is more the CPack's job, however I understand your point.
>>
>> An extra target may be a small price to pay, no?
>
>
> Well I'd rather have a so
Hi,
>
>
> First of all, you definitely need the library target in order to build
> the library, and CMake ignores each file in the list of sources which
> is not necessary for this purpose. IMO, that's quite reasonable; e.g.,
> you wouldn't want to have the library relinked or even completely re-
On 12/14/2011 09:30 AM, Alexander Broekhuis wrote:
> Hi,
>
>
>> CMake takes great care regarding dependencies on files which are needed
>> to build targets, i.e. usually, it's not necessary to specify any extra
>> dependencies of a target on a file. In my exemplary project, the README
>> file is
Hi,
Thanks for you replies,
> > In my case the output is the ZIP file. So the zip file is produced by the
> > top level target, and I don't want/need a separate target for it.
>
> Yes but CMake's jobs is to build libraries and executables not "bundle"
> which is more the CPack's job, however I u
2011/12/14 Alexander Broekhuis :
> Hi,
>
>>
>> CMake takes great care regarding dependencies on files which are needed
>> to build targets, i.e. usually, it's not necessary to specify any extra
>> dependencies of a target on a file. In my exemplary project, the README
>> file is actually not needed
On 12/13/2011 4:15 PM, David Cole wrote:
RUNTIME_OUTPUT_DIRECTORY is a target property, not a variable. You'd
have to use get_property to retrieve its value, not
${RUNTIME_OUTPUT_DIRECTORY}...
Thanks! I ended up with the following, in the targets CMakeList file
get_property(exe_path TARGET ${
Dear developers,
Initial warning: This is a minor issue.
One of the computers that are submitting nightlies to my cdash server
is an iMac which does not have /usr/local created. However, it looks
like /usr/loca/lib is one of the default directories which is linked,
so his report always has a link
Hi,
> CMake takes great care regarding dependencies on files which are needed
> to build targets, i.e. usually, it's not necessary to specify any extra
> dependencies of a target on a file. In my exemplary project, the README
> file is actually not needed to build the library target, so CMake doe
22 matches
Mail list logo
