Bill Hoffman wrote:
> Eric Noulard wrote:
>
>> That's true, may be the site could indicate that the doc is for latest
>> 2.6.x serie.
>> However the most trustfull way to check the doc of your current cmake
>> version is the command line.
>>
>> cmake --help-command if
>>
>> should give you the doc
Eric Noulard wrote:
That's true, may be the site could indicate that the doc is for latest
2.6.x serie.
However the most trustfull way to check the doc of your current cmake
version is the command line.
cmake --help-command if
should give you the doc for the cmake version you are using.
if yo
2010/2/5 Mateusz Loskot :
> Hi,
>
> Perhaps it will be helpful information for someone.
> On popular Linux distributions CMake 2.6 may not be necessarily the same
> CMake 2.6 as documented [1] on the website.
>
> CMake from Ubuntu 9.10 reports "cmake version 2.6-patch 4"
> CMake from Debian 5.0.3
Hi,
Perhaps it will be helpful information for someone.
On popular Linux distributions CMake 2.6 may not be necessarily the same
CMake 2.6 as documented [1] on the website.
CMake from Ubuntu 9.10 reports "cmake version 2.6-patch 4"
CMake from Debian 5.0.3 reports "cmake version 2.6-patch 0"
It'
On Tuesday 02 February 2010, Schwartz, Philip wrote:
> My current project has many components that need to be built. Some portions
> of our code depend on others and using add_subdirectory, I am having an
> issue where I get multiple of my targets loaded causing a faliure.
>
> I placed the add_subd
Theodore Papadopoulo wrote:
> I'm attaching (for comments) a modified FortranCInterface.cmake that
> basically has two modes. If a fortran and
> a C compiler are available, it works as it does currently except for teo
> things:
> - Error messages when C or Fortran compiler is missing should be much
I have been following this discussion silently, as the problem of
interfacing C/C++ with blas and lapack
(and without obliging users to install a fortran compiler) is recurrent
in a few of the projects I'm involved in.
I'm attaching (for comments) a modified FortranCInterface.cmake that
basica
Instead of using the LOCATION property, you might consider doing
something along these lines, using the LOCATION_Release, LOCATION_Debug,
etc. properties. I do something similar to this on windows/MSVC to toss
extra files around that have an executable's full path:
foreach(_configname ${CMAKE_
2010/2/5 Surya Kiran Gullapalli :
> Hello all,
> I'm using CMake-2.8 on winxp with Visual Studio 2005 generator.
> lets say I've a dll created (A.dll) from some cxx files and a static library
> static.lib
> So I call Link_Directories to specify the directory where the static library
> is located.
On 5. Feb, 2010, at 14:37 , Surya Kiran Gullapalli wrote:
> Hello all,
> I'm using CMake-2.8 on winxp with Visual Studio 2005 generator.
>
> lets say I've a dll created (A.dll) from some cxx files and a static library
> static.lib
>
> So I call Link_Directories to specify the directory where th
Response Below
Inline...
On Fri, Feb 5, 2010 at 12:05 AM, Alan W. Irwin
wrote:
> On 2010-02-04 22:44-0600 Tim St. Clair wrote:
>>
>> On Thu, Feb 4, 2010 at 6:14 PM, Alan W. Irwin
>> wrote:
>>>
>>> Why not simply use install(FILES ... PERMISSIONS RENAME ... )?
>>>
>>> You would have to use
Hello all,
I'm using CMake-2.8 on winxp with Visual Studio 2005 generator.
lets say I've a dll created (A.dll) from some cxx files and a static library
static.lib
So I call Link_Directories to specify the directory where the static library
is located.
Now A.dll is built fine.
Now I want B.dll bu
Hi everybody, first sorry for the long intro,
I' m trying to build up a project that assembles different components,
all open source and portable.
The main component is OpenSceneGraph that heavily relies on FindXXX to
do configure time inspection and conditionally build plug ins.
I am trying
Am Freitag, den 05.02.2010, 09:51 +0100 schrieb Michael Wild:
>
> Hmmm, that appears to be a bug. Anyways, I usually call the EXPORT something
> like TLibExports or TLibTargets.
You are right, this is the best solution
Micha
___
Powered by www.kitw
On 5. Feb, 2010, at 9:18 , Micha Renner wrote:
> I install a library (TLib) and their export files with these commands:
>
> INSTALL(TARGETS TLib EXPORT TLibX RUNTIME DESTINATION dll
> LIBRARY DESTINATION lib
> ARCHIVE DE
I install a library (TLib) and their export files with these commands:
INSTALL(TARGETS TLib EXPORT TLibX RUNTIME DESTINATION dll
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib)
INSTALL(EXPORT TLibX NAMESPACE mp_ DEST
16 matches
Mail list logo