Brad King schrieb am Freitag 13 März 2009 um 16:51:
> The full fix is of course to discard 'C'-prefixed comments completely,
> but that can only be done in fixed-form sources. Currently our lexer
> has code to support fixed-form files but it is never enabled. CMake
> does not know whether a sourc
Eric Noulard schrieb am Freitag 13 März 2009 um 19:00:
> which makes me think that ALL rules in the lexer are
> currently ignored
> because the start condition never gets activated.
> i.e. there should be some code that's tell the lexer that it is lexing
> a fixed format file.
>
> Note that this
> Is this causing issues with the building of your project? Or is it just ugly
> to look at?
>
Bill,
I am not the OP but I use cmake 2.6.3 since it was released with
vs2005 but for me I can not see any difference besides the ugly symbol
in the solution explorer.
John
_
Hicham Mouline wrote:
Hello,
cmake 2.6.3.
There has been a number of modifications which have caused all headers in the
generated project files .vcproj to be excluded frm build
(the red minus sign next to the file in Solution explorer)
I have searched from inside VStudio the string HEADER_ONLY
> cmake 2.6.3.
> There has been a number of modifications which have caused all headers in the
> generated project files .vcproj to be excluded frm build
> (the red minus sign next to the file in Solution explorer)
>
> I have searched from inside VStudio the string HEADER_ONLY (ignoring case) in
Hello,
cmake 2.6.3.
There has been a number of modifications which have caused all headers in the
generated project files .vcproj to be excluded frm build
(the red minus sign next to the file in Solution explorer)
I have searched from inside VStudio the string HEADER_ONLY (ignoring case) in
all
John
Thanks for this info. The version I compiled from the boost-cmake svn
repository was 1.36 so I didn't realize that the main branch had it
included.
I'll give 1.38 a try.
JB
Will standard releases of Boost
contain CMakeLists files in my lifetime?
They do
It's not very elegant, but this will have the desired effect:
1. make sure the library SUBDIR is in your CMakeLists.txt before any
other subdir that depends on it.
2. use add_custom_command to copy the library, once built, into each subdir.
3. use install in each subdir to install the library wher
On Fri, Mar 13, 2009 at 3:09 PM, John Drescher wrote:
> On Fri, Mar 13, 2009 at 3:08 PM, John Drescher wrote:
>>> Will standard releases of Boost
>>> contain CMakeLists files in my lifetime?
>>
>> They do already. 1.38.0 did. Although I did not have good success
>> building it that way.
>>
> Here
On Fri, Mar 13, 2009 at 3:08 PM, John Drescher wrote:
>> Will standard releases of Boost
>> contain CMakeLists files in my lifetime?
>
> They do already. 1.38.0 did. Although I did not have good success
> building it that way.
>
Here is a link to the release notes (look at the bottom of the page):
> Will standard releases of Boost
> contain CMakeLists files in my lifetime?
They do already. 1.38.0 did. Although I did not have good success
building it that way.
John
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:/
I would ask on the boost-cmake mailing list. You will probably get
good replies from notable people from the boost project.
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.n
Hi Alex,
first of all thanks for the reply.
The reason is simple, I want to distribute each tool with all the
libraries needed to run.
You said that the library will be installed only once...is it possible
to decide where install the library
within the "CMakeFile" of each single tools? It'
2009/3/13 Maik Beckmann :
> Brad King schrieb am Freitag 13 März 2009 um 16:51:
>> Actually, I cannot tell from a quick glance at the code how it ignores
>> 'USE' keywords that appear after a ';' separator. It does not ignore
>> 'MODULE' after ';'. Maik?
>
> If a piece of code is identifed by the
On Fri, Mar 13, 2009 at 1:39 PM, Alexander Neundorf
wrote:
> On Friday 13 March 2009, John Drescher wrote:
>> Is there a way to have cmake automatically create empty missing source
>> files instead of failing?
>
> No, there is not.
>
>> Basically I when I need to add new files I add new entries to
On Friday 13 March 2009, Daniele Galdi wrote:
> Hi,
>
> I have a project structure like this in my cmake project.
>
> project/src/core-lib
> project/src/tool1
> project/src/tool2
> project/src/tool3
>
> the core library is a shared library. Each tool links this lib, what i
> want to achieve is deci
On Friday 13 March 2009, John Drescher wrote:
> Is there a way to have cmake automatically create empty missing source
> files instead of failing?
No, there is not.
> Basically I when I need to add new files I add new entries to my
> CMakeLists.txt file then I have to go to the shell and touch on
2009/3/13 Denis Scherbakov :
>
> Eric,
>
> Your solution requires a developer to know too much about the project, which
> is not always true and basically to answer a full-scale questionnaire before
> compilation. What if it is a new developer?
If it is not a developer there is a simpler solutio
Brad King schrieb am Freitag 13 März 2009 um 16:51:
> Actually, I cannot tell from a quick glance at the code how it ignores
> 'USE' keywords that appear after a ';' separator. It does not ignore
> 'MODULE' after ';'. Maik?
If a piece of code is identifed by the _lexer_ as being a comment, it is
On Fri, Mar 13, 2009 at 1:15 PM, Denis Scherbakov
wrote:
>
> John,
>
> You may want to look into ADD_CUSTOM_COMMAND.
>
>
> PROJECT(CORBASAMPLE)
>
> ADD_CUSTOM_COMMAND(
> OUTPUT "${PROJECT_BINARY_DIR}/MyMicoGeneratedSource.cpp"
> COMMAND "${MICO_IDL_EXECUTABLE}" --hh-suffix=h
John,
You may want to look into ADD_CUSTOM_COMMAND.
PROJECT(CORBASAMPLE)
ADD_CUSTOM_COMMAND(
OUTPUT "${PROJECT_BINARY_DIR}/MyMicoGeneratedSource.cpp"
COMMAND "${MICO_IDL_EXECUTABLE}" --hh-suffix=hh --any --poa
${PROJECT_SOURCE_DIR}/IdlSource.idl)
SET_SOURCE_FILES_PROP
Denis Scherbakov wrote:
Eric,
Your solution requires a developer to know too much about the
project,
which is not always true and basically to answer a full-scale
questionnaire before compilation. What if it is a new developer? What if
it is not a developer, but a user who expects everything to
Andreas Schneider wrote:
Hi,
what means
- Fix set cache FORCE and -D command line to work together
I've recognized, that -DFOO=something doesn't overwrite cache settings anymore
which are set to FORCE. Is this true?
If yes, then the documentation should be updated. -D states:
Eric,
Your solution requires a developer to know too much about the project, which is
not always true and basically to answer a full-scale questionnaire before
compilation. What if it is a new developer? What if it is not a developer, but
a user who expects everything to compile automatically?
Is there a way to have cmake automatically create empty missing source
files instead of failing?
Basically I when I need to add new files I add new entries to my
CMakeLists.txt file then I have to go to the shell and touch on each
file I add so that cmake will not fail to regenerate the project.
2009/3/13 Eric Noulard :
My statement was ambiguous:
>
> cmake -DBUILD_PRINTF:BOOL=OFF
The previous line is meant to avoid building the PRINTF project
while...
> in this case the default is to build both.
The default value of options
BUILD_PRINTF
BUILD_PUTS
is to build both such that if not
2009/3/13 Denis Scherbakov :
>
> As I already wrote, my problem is that "IF ( NOT MICO_FOUND )" code is
> executed too early - during compilation by cmake, not when user types "gmake
> puts" and it becomes clear that MICO is needed.
That's the expected behavior, because CMake tries to find libX
Hi,
what means
- Fix set cache FORCE and -D command line to work together
I've recognized, that -DFOO=something doesn't overwrite cache settings anymore
which are set to FORCE. Is this true?
If yes, then the documentation should be updated. -D states:
This option may be used t
Dear Marcel Loose,
I tried what you have suggested and it doesn't work also.
Here is what I have:
=CMakeLists.txt
CMAKE_MINIMUM_REQUIRED(VERSION 2.6.1 FATAL_ERROR)
ADD_SUBDIRECTORY("printf")
ADD_SUBDIRECTORY("puts")
ADD_SUBDIRECTORY("forbug")
SET(MAIN_SRCS
main.cpp)
INCLUDE_DI
Hi Denis,
If only project SOMENAME in directory targetA depends on LibXml2, then
you should move the line INCLUDE(FindLibXml2) to the file
targetA/CMakeLists.txt.
BTW, I'd prefer to use find_package(LibXml2), but that may be a matter
of taste.
Best regards,
Marcel Loose.
On Fri, 2009-03-13 at 0
Bill Hoffman wrote:
>> The following Fortran code cannot be compiled with CMake, because
>> CMake looks for module called "name", which of course, does not exist.
Actually it thinks the source is defining a module called "name".
>> If I replace "Module" with "_Module_" the code compiles.
>> =
I just did an svn update of a very old boost-cmake folder and ran cmake.
Everything built with no errors (Visual studio 2008) (lots of warnings,
but no errors).
I wonder.
How well is CMakeification of Boost going? Will standard releases of
Boost contain CMakeLists files in my lifetime? and if
> I don't understand the question here? At gmake time
> why do they need to know anything about mico or libxml2?
Ok, I will try harder now:
Let's say I have a main CMakeLists.txt and 2 sub projects:
=CMakeLists.txt
CMAKE_MINIMUM_REQUIRED(VERSION 2.6.1 FATAL_ERROR)
INCLUDE(FindLibX
Denis Scherbakov wrote:
Dear CMake list subscripers,
I have a project with verious ADD_LIBRARY/ADD_EXECUTABLE targets in
different subdirectories. Some of these targets depend on mico corba,
some don't. As well as some depend on libxml2, some don't.
We have developers working on sub-projec
Dear CMake list subscripers,
I have a project with verious ADD_LIBRARY/ADD_EXECUTABLE targets in different
subdirectories. Some of these targets depend on mico corba, some don't. As well
as some depend on libxml2, some don't.
We have developers working on sub-projects, which do not require mic
Claus Höfele wrote:
Thanks for the quick replies.
I'm using cmake 2.6.3 + Visual Studio 8 2005 SP1
Playing around further with the file properties in Visual Studio, it
looks like VS only checks the syntax of a file if the Tool property is
set to C/C++ Compiler Tool. However, this setting will c
09/3/13 Philip Lowman :
> On Thu, Mar 12, 2009 at 7:39 PM, Bart Janssens
> wrote:
>>
>> Not sure if this ever came up, but I'm struggling with FindBoost and
>> the boost system library. The system library is required from boost
>> 1.35 onwards, but doesn't exist in earlier versions. Is there a way
Am Donnerstag, 12. März 2009 09:37:12 wrote Adolfo Rodríguez:
> We currently use three of CMake's generators: "Unix Makefiles",
> "KDevelop3", and "Eclipse CDT4 - Unix Makefiles", and we're interested in
> doing parallel builds.
I use the environment variable MAKEFLAGS
before starting eclipse, i
Hi,
I have a project structure like this in my cmake project.
project/src/core-lib
project/src/tool1
project/src/tool2
project/src/tool3
the core library is a shared library. Each tool links this lib, what i
want to achieve is decide
where install the core-lib in each tool. eg. tool1 install
2009/3/13 Mattias Helsing
> Hello Ankit,
>
> On 3/13/09, ankit jain wrote:
> > Hi all,
> >
> > I have a shell script. I want to link it with a library that i have build
> > using cmake. Is it possible to do so.
> > I am running this shell script using cmake.
>
> You need to describe what you wan
On Thu, Mar 12, 2009 at 10:56 PM, Alexander Neundorf <
a.neundorf-w...@gmx.net> wrote:
> On Thursday 12 March 2009, Bill Hoffman wrote:
> > Alexander Neundorf wrote:
> > >> I'm using CMake 2.6.2 and Eclipse CDT5 (not CDT4, could this be an
> > >> issue?)
> > >
> > > I don't think so.
> > > We coul
2009/3/10 Sharon Melamed
> Hi,
>
>
>
> My main CmakeList.txt file look like this:
>
>
>
> cmake_minimum_required (VERSION 2.6)
>
> project (vos)
>
Same thing happens to me also. The problem is of RPATH settings. the path
your cmakelist links to while installing is not set for the sub directorie
42 matches
Mail list logo
