On Feb 16, 2008 3:48 PM, Alexander Neundorf [EMAIL PROTECTED] wrote:
Any opinion whether RAISE_SCOPE/PARENT_SCOPE should propagate to the parent
directory if it's used outside a function ?
What if I do want a variable to propagate up through nested
functions functions, but I don't want any
Quoting Brandon Van Every [EMAIL PROTECTED]:
I have to admit, PARENT_SCOPE nomenclature bugs me. I don't know of
any mainstream programming language that explicitly asks me to think
about scope when setting a variable.
Ruby asks. But it does so in a so nicely and clear way that you
On Feb 17, 2008 6:01 AM, Pau Garcia i Quiles [EMAIL PROTECTED] wrote:
As a reminder, here comes the nomenclature in Ruby:
Scope Prefix Example
- -- ---
global variable $$global
instance variable @
Ok this was yet-another-weird-dll thingy, one cannot do:
class GDCM_EXPORT String : std::string { ... }
std::string is already exported (dllexport/dllimport) which was
causing the linker to complain...
As a side note, the free toolkit + a recent PSDK does have all the c
standard libs now. I
Lets assume for a second that your layout is something like:
Project
src
-sub1
--CMakeLists.txt
--sub1.cpp
--sub1.ui
-sub2
--CMakeLists.txt
--sub2.cpp
What you would want quite possible is a top level CMakeLists.txt file
Like this:
PROJECT (MyGreatProject)
On 02/17/2008 04:51 PM, Mike Jackson wrote:
Lets assume for a second that your layout is something like:
Project
src
-sub1
--CMakeLists.txt
--sub1.cpp
--sub1.ui
-sub2
--CMakeLists.txt
--sub2.cpp
What you would want quite possible is a top level
On Sunday 17 February 2008, blinkeye wrote:
Hi guys
I'm in the process of replacing Makefiles from two large projects with
CMake files. So far it's working great, but now I hit a wall:
I need to generate .cpp and .h files from input files (analogue to the
.ui files of Qt).
...
Imagine the
On 02/17/2008 04:58 PM, Alexander Neundorf wrote:
On Sunday 17 February 2008, blinkeye wrote:
Hi guys
I'm in the process of replacing Makefiles from two large projects with
CMake files. So far it's working great, but now I hit a wall:
I need to generate .cpp and .h files from input files
When i add this line to CMakeLists.txt i get a segmentation fault
cmake version 2.4-patch 6
The problem seems to appear when the relative path ends with '/'
FILE (GLOB TESTS ./test/ *.cpp)
___
CMake mailing list
CMake@cmake.org
Hi,
attached you can find a patch against current cmake cvs which adds support for
generating the documentation as docbook file.
(the patch is not yet ready to apply, it must still be cleaned up and
documentation for that feature has to be added).
docook is useful as a bse format to convert
On Sunday 17 February 2008, pepone.onrez wrote:
When i add this line to CMakeLists.txt i get a segmentation fault
cmake version 2.4-patch 6
The problem seems to appear when the relative path ends with '/'
FILE (GLOB TESTS ./test/ *.cpp)
I can't reproduce it:
$ cat CMakeLists.txt
FILE
On Feb 17, 2008 2:13 PM, Alexander Neundorf [EMAIL PROTECTED] wrote:
attached you can find a patch against current cmake cvs which adds support for
generating the documentation as docbook file.
Interesting. I started going up a learning curve recently about
technical documentation formats,
On Feb 17, 2008, at 2:13 PM, Alexander Neundorf wrote:Can this e.g. in some way be used with Qt assistant ? Attached is the hack that I use to get QtAssistant based docs for CMake. It is a bash shell script. Could probably be written in CMake if needed. It has helped me quickly find needed
Folks,
Most CMake projects use TRY_COMPILE and CMake macros to test for include
files, flags, capabilities of the compiler etc. The CMake/Modules macros
append the output of these commands to
${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log or
Bill Lorensen wrote:
Folks,
Most CMake projects use TRY_COMPILE and CMake macros to test for include
files, flags, capabilities of the compiler etc. The CMake/Modules macros
append the output of these commands to
${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log or
Hi all,
Maybe it is a simple question, but I really have no answer. So, hope you
could help me.
Here is my directories tree :
|_ src __
| |_ geometrie
| |_ truc
|
|_ test __
|_ geometrie
|_ truc
In test, I have this CMakeLists.txt :
I have tried using the --debug-output command line option but it doesn't seem to
change anything. Can someone elaborate on this? I'm not trying to debug
anything in particular just curious.
--
Daniel
___
CMake mailing list
CMake@cmake.org
17 matches
Mail list logo
