I downloaded and installed the latest version of CMake 2.8.8. I found
problems with the FindBLAS, FindLAPACK modules.
First thing I noticed was the ACML library search does not work for
versions > 5.0. ACML no longer distributes acml_mv (multivector library)
with ACML for versions > 5.0. Fin
Hi Dan,
I don't think it's possible to set compiler flags on a
per-configuration, per-target basis without splitting your project.
There was a very similar discussion recently [1],[2] which indicated a
couple of options. However the first option can't be used on a
per-configuration basis, w
FYI -- CMake 2.8.8 was released the evening of April 18, and we have
scheduled this webinar about the new stuff that's in it. But. we have
had to adjust the time slightly. It will now occur on Tuesday, April 24,
2012 at *2:15 pm Eastern* time.
Register for it here if you're interested:
https
2012/4/20 Nicolas Desprès :
> 2012/4/20 David Cole :
>> 2012/4/20 Nicolas Desprès :
>>> 2012/4/20 Eric Noulard :
Le 20 avril 2012 13:40, Nicolas Desprès a
écrit :
> 2012/4/20 Eric Noulard :
>> Le 20 avril 2012 10:44, Nicolas Desprès a
>> écrit :
>>> Hi,
>>>
>>>
On Fr., 20. Apr. 2012 11:23:08 CEST, Nicolas Desprès
wrote:
> On Fri, Apr 20, 2012 at 10:58 AM, Rolf Eike Beer wrote:
> > > Hi,
> > >
> > > I have noticed that most cmake based projects document their options
> > > in their README file whereas the documentation is already included in
> > > cma
I'm trying to write a CMake patch script for a package that needs a
TARGET_LINK_LIBRARIES command replaced.
In the original it covers multiple lines, e.g.
TARGET_LINK_LIBRARIES(targetname1
boguslib1
boguslib2
boguslib3
)
I tried this to replace it:
string(REGEX REPLACE "TARGET_LINK_LIBRARIES(ta
2012/4/20 David Cole :
> 2012/4/20 Nicolas Desprès :
>> 2012/4/20 Eric Noulard :
>>> Le 20 avril 2012 13:40, Nicolas Desprès a écrit
>>> :
2012/4/20 Eric Noulard :
> Le 20 avril 2012 10:44, Nicolas Desprès a
> écrit :
>> Hi,
>>
>> I would like to have your opinion befor
Hi,
I have a situation where I need to package up a build for
installation where there are two available license choices
(1) Non-commercial/evaluation
(2) Commercial
For the NSIS packaging, is there a way to show different licensing
text depending on some radio button choice?
Also, is
Hi
I'm looking for query features in CMake.
In a very complex and large project with 100's of packages, developped
by many persons, each responsible of a subset, but forming a complex
graph of interrelated stuff, it important to be able to query the
configuration (at least for debugging purpo
2012/4/20 Nicolas Desprès :
> 2012/4/20 Eric Noulard :
>> Le 20 avril 2012 13:40, Nicolas Desprès a écrit :
>>> 2012/4/20 Eric Noulard :
Le 20 avril 2012 10:44, Nicolas Desprès a
écrit :
> Hi,
>
> I would like to have your opinion before to start to implement it.
>
Thanks to all who gave me hints and recipes to use CMake. And this
works. Great!
Christian
Le 20/04/2012 13:41, Petr Kmoch a écrit :
I never used --build myself, but my guess is you can't generate and
build the project in a single step. I'd try the following (on a blank
setup):
cd test/B/bu
2012/4/20 Eric Noulard :
> Le 20 avril 2012 13:40, Nicolas Desprès a écrit :
>> 2012/4/20 Eric Noulard :
>>> Le 20 avril 2012 10:44, Nicolas Desprès a écrit
>>> :
Hi,
I would like to have your opinion before to start to implement it.
I would like to add the following opt
Le 20 avril 2012 13:40, Nicolas Desprès a écrit :
> 2012/4/20 Eric Noulard :
>> Le 20 avril 2012 10:44, Nicolas Desprès a écrit :
>>> Hi,
>>>
>>> I would like to have your opinion before to start to implement it.
>>>
>>> I would like to add the following options to the cmake command line
>>> int
2012/4/20 Christian Arnault :
> Hi
>
> [I am on windows]
>
> If I use cmake-gui to build my project, it starts asking me for the build
> directory. Which is OK!
>
> (my project is named "B", it stands in "test/B", where there is a
> "test/B/CMakeLists.txt" and I want to build into "test/B/build")
>
2012/4/20 Eric Noulard :
> Le 20 avril 2012 10:44, Nicolas Desprès a écrit :
>> Hi,
>>
>> I would like to have your opinion before to start to implement it.
>>
>> I would like to add the following options to the cmake command line
>> interface:
>> --help-option opt [file] = Print help for a giv
I never used --build myself, but my guess is you can't generate and
build the project in a single step. I'd try the following (on a blank
setup):
cd test/B/build
cmake ..
cmake --build .
When running cmake from the command line to generate a buildsystem,
the source directory (where CMakeLists.txt
2012/4/20 Andrea Crotti :
> On 04/19/2012 07:00 PM, Eric Noulard wrote:
>>
>> Compiler, Visual Studio something?
>> You run cpack from the command line or from within IDE/Makefile etc
>>
>
> No compilers used for this project (it's python) and I run from command
> line.
>
> Anyway it might be a
On 04/19/2012 07:00 PM, Eric Noulard wrote:
Compiler, Visual Studio something?
You run cpack from the command line or from within IDE/Makefile etc
No compilers used for this project (it's python) and I run from command
line.
Anyway it might be a good idea also in general so I tried to d
Hi
[I am on windows]
If I use cmake-gui to build my project, it starts asking me for the
build directory. Which is OK!
(my project is named "B", it stands in "test/B", where there is a
"test/B/CMakeLists.txt" and I want to build into "test/B/build")
Now, if I use command interface CMake as
Le 20 avril 2012 10:44, Nicolas Desprès a écrit :
> Hi,
>
> I would like to have your opinion before to start to implement it.
>
> I would like to add the following options to the cmake command line interface:
> --help-option opt [file] = Print help for a given option and exit.
> --help-option-l
On Fri, Apr 20, 2012 at 10:58 AM, Rolf Eike Beer wrote:
>> Hi,
>>
>> I have noticed that most cmake based projects document their options
>> in their README file whereas the documentation is already included in
>> cmake when you call the option() and set() commands. I hope this
>> feature will hel
> Hi,
>
> I have noticed that most cmake based projects document their options
> in their README file whereas the documentation is already included in
> cmake when you call the option() and set() commands. I hope this
> feature will help to remove this duplication and people will just
> write in th
Hi,
I would like to have your opinion before to start to implement it.
I would like to add the following options to the cmake command line interface:
--help-option opt [file] = Print help for a given option and exit.
--help-option-list [file] = List available options and exit.
--help-options [
Hi Petr,
Thanks for your advices which goes on the line I already explored.
Indeed I have played a bit with similar constructions (either using
functions or macros) and yes it works (simply I thought I had missed
some features in CMake)
One point which forced me to manually add some tricks t
I love cmake, but I am still a bit of a novice, so perhaps there is a
better way to approach this problem. I am building a library using
cmake. On Windows I need to be able to build two versions: one that
links statically to the CRT (/MT) and one that links dynamically to
the CRT (/MD). I would
25 matches
Mail list logo