Alexander Neundorf escreveu:
> Is propagating the value up to the parent directory really a good idea ? If
> people want to do that (get some information from somewhere deep in the tree
> up to some other place) they can use a global property.
> I feel like removing the else{} part in cmMakefile
On Friday 18 January 2008, Andreas Pakulat wrote:
> On 18.01.08 22:39:17, Alexander Neundorf wrote:
> > On Friday 18 January 2008, Andreas Schneider wrote:
> > > It is
> > >
> > > /opt/local
> >
> > This one is already, at least cmake cvs.
>
> Do you mean that cmake cvs always looks in /opt/local u
On 18.01.08 22:39:17, Alexander Neundorf wrote:
> On Friday 18 January 2008, Andreas Schneider wrote:
> > It is
> >
> > /opt/local
>
> This one is already, at least cmake cvs.
Do you mean that cmake cvs always looks in /opt/local unless
NO_DEFAULT_PATHS are specified?
Andreas
--
You enjoy the
On Friday 18 January 2008, Andreas Schneider wrote:
> Andreas Pakulat wrote:
> > On 17.01.08 23:41:54, Andreas Schneider wrote:
> >> Andreas Pakulat wrote:
> >>> On 14.01.08 23:40:39, Andreas Schneider wrote:
> Rodolfo Schulz de Lima wrote:
> > Hi, I'd like to comment on the Find*.cmake va
Andreas Pakulat wrote:
> On 17.01.08 23:41:54, Andreas Schneider wrote:
>> Andreas Pakulat wrote:
>>> On 14.01.08 23:40:39, Andreas Schneider wrote:
Rodolfo Schulz de Lima wrote:
> Hi, I'd like to comment on the Find*.cmake variable naming procedure
> adopted by cmake. Right now I have
On Friday 18 January 2008, Ken Martin wrote:
> > Yes, and I'll also remove raise_scope() then. Ok ?
>
> Yuppers - Ken
Done.
I noticed that almost all calls are now:
set( ${} PARENT_SCOPE)
Is propagating the value up to the parent directory really a good idea ? If
people want to do that (get som
On Jan 18, 2008 4:59 AM, Rodolfo Lima <[EMAIL PROTECTED]> wrote:
> Brandon Van Every escreveu:
>
> > The dependencies of an add_custom_command are completely under your
> > control anyways. You specify them. Why don't you just re-specify
> > them in your command?
>
> It's a bit burdensome when th
Radu Serban wrote:
I generate a script (shell on *nix, *.bat on windows) using FILE(WRITE
which I then install using INSTALL(PROGRAMS so that the permissions are
set properly. However, I'd like to first test it from within CMake using
EXECUTE_PROCESS but that obviously fails since the script do
> Yes, and I'll also remove raise_scope() then. Ok ?
Yuppers - Ken
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
I generate a script (shell on *nix, *.bat on windows) using FILE(WRITE which
I then install using INSTALL(PROGRAMS so that the permissions are set
properly. However, I'd like to first test it from within CMake using
EXECUTE_PROCESS but that obviously fails since the script does not have
execute
On Jan 18, 2008 1:50 PM, Brandon Van Every <[EMAIL PROTECTED]> wrote:
> Check the FAQ and the mailing list archives for more info on this issue.
Sorry, the FAQ doesn't have any clear statement on the "static lib
inside a static lib" issue. It does talk about so-called
"convenience" libraries a bi
On Jan 18, 2008 4:18 AM, Ramazan Girgin <[EMAIL PROTECTED]> wrote:
> Hi all,
> I am building static lib on windows.While building static lib i am using
> external static library . With using cmake a couldn't add this static
> library to my new static library.
Some archivers such as AR cannot put a
Hello,
I tried (unsuccessfully) to figure out a way to minimize the number of times
a sub-module is configured so I thought I'll ask for advice. My situation is
such that the configuration of a particular submodule can be very lengthy
(lots of code generation and transformation) and therefore,
On 2008-01-18 13:43+0100 Yang, Y. wrote:
Hi all.
I just use CMake for two week. And I found it's very good tool.
However, I just wonder that why in CMake the SET not support regular
expression.
For example, SET( MY_SRCS mydir/*.c)
if CMake can do this, I don't have to modify the CMakeLists.tx
On Friday 18 January 2008, Ken Martin wrote:
> I think the patch to the set command is probably the best bet. Raise_scope
> could be made to do the same thing but honestly the changes to set are
> pretty simple and that clears up some confusion about raise scope not
> setting the local variable and
I think the patch to the set command is probably the best bet. Raise_scope
could be made to do the same thing but honestly the changes to set are
pretty simple and that clears up some confusion about raise scope not
setting the local variable and not actually raising the local variable's
setting. A
On Friday 18 January 2008, Rodolfo Schulz de Lima wrote:
> Miguel A. Figueroa-Villanueva wrote:
> > Again, I think this behaviour is a quite unintuitive and should be
> > well documented, at least.
>
> I shall add that at first I expected 'raise_scope' to work like 'set'
> when the parameter is a
Miguel A. Figueroa-Villanueva wrote:
Again, I think this behaviour is a quite unintuitive and should be
well documented, at least.
I shall add that at first I expected 'raise_scope' to work like 'set'
when the parameter is a list. But, for instance:
set(mylist item1 item2 item3)
set(var1
On Dec 28, 2007 12:52 PM, Miguel A. Figueroa-Villanueva wrote:
> On Dec 28, 2007 11:36 AM, Ken Martin wrote:
> > > > > 1. CMake crashes if I use the same variable name as the argument and
> > > > > raise the scope later. That is, for the following function:
>
>
>
> > Specifically
> >
> > Variable
If you do a FILE(GLOB cmake will not detect when files are added to the
directory and will *not* re-run automatically. If you explicitly list your
files in CMakeLists.txt, then when it changes, cmake re-runs automatically
as part of a build.
Don't use the FILE(GLOB technique unless you are willing
On Jan 18, 2008 11:43 PM, Yang, Y. <[EMAIL PROTECTED]> wrote:
> For example, SET( MY_SRCS mydir/*.c)
>
> if CMake can do this, I don't have to modify the CMakeLists.txt every
> time when I add new files to mydir.
>
> That's not exactly a regular expression - it's a glob.
In any case, FILE(GLOB ...
Hi all.
I just use CMake for two week. And I found it's very good tool.
However, I just wonder that why in CMake the SET not support regular
expression.
For example, SET( MY_SRCS mydir/*.c)
if CMake can do this, I don't have to modify the CMakeLists.txt every
time when I add new files to mydir.
Brandon Van Every escreveu:
> The dependencies of an add_custom_command are completely under your
> control anyways. You specify them. Why don't you just re-specify
> them in your command?
It's a bit burdensome when the dependencies exceed the count of 10 or
20. Ok, I could create them in a var
Hi all,
I am building static lib on windows.While building static lib i am using
external static library . With using cmake a couldn't add this static
library to my new static library.
I used TARGET_LINK_LIBRARY comment but it is not linking staticly.How can i
do this with cmake?
Thanks in advance.
On 17.01.08 23:41:54, Andreas Schneider wrote:
> Andreas Pakulat wrote:
> > On 14.01.08 23:40:39, Andreas Schneider wrote:
> >> Rodolfo Schulz de Lima wrote:
> >>> Hi, I'd like to comment on the Find*.cmake variable naming procedure
> >>> adopted by cmake. Right now I have to look at some Find*.cma
25 matches
Mail list logo
