Hello,
I am trying to set a variable in an IF block, but it doesn't appear in
the resulting cache or makefile. This is on Linux. Note that when I
run cmake, the ${OSNAME} variable is printed, but the ${FOOBAR} variable
ends up blank.
Thanks,
Juan
IF (${OSNAME} STREQUAL Linux64)
MESSAGE
My apologies, it turns out there was a syntax error, that was not fatal,
and not mentioned in the debug output.
Thanks,
Juan
Juan Sanchez wrote:
Hello,
I am trying to set a variable in an IF block, but it doesn't appear in
the resulting cache or makefile. This is on Linux. Note
. Every time I type make, the object file
gets recreated.
ADD_CUSTOM_COMMAND(
OUTPUT ${PSTUFF}.o
DEPENDS ${PSTUFF}.cc
COMMAND ${CMAKE_CXX_COMPILER}
ARGS ${MYFLAGS}
)
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
in a better way, I'd appreciate that info too.
Regards,
Juan
Alexander Neundorf wrote:
On Monday 30 July 2007 16:24, Juan Sanchez wrote:
Is there a command for creating a .o target on Linux? If I create my
own custom command for creating an object, the .o file is being
recompiled every time
Montag 30 Juli 2007 22:44 schrieb Juan Sanchez:
It's pretty messy the Makefile I am trying to convert. It is trying to
do something like this:
g++ -shared obj1.o obj2.o obj3.o staticarchivex.a staticarchivey.a -o
sharedlibrary.so
The static archives are compiled with -fPIC so dynamic relocation
of the static library
arguments.
Thanks again,
Juan
Hendrik Sattler wrote:
Am Montag 30 Juli 2007 23:39 schrieb Juan Sanchez:
Did you try to make it straight-forward without any tweaking around?:
add_library (staticarchivex STATIC ...)
add_library (staticarchivey STATIC ...)
add_library (sharedlibrary
Thanks everyone for their help. I'm evaluating cmake for my group and
it appears that cmake meets many of the needs that we have.
Regards,
Juan
Hendrik Sattler wrote:
Am Dienstag 31 Juli 2007 00:16 schrieb Juan Sanchez:
Thanks for the make VERBOSE=1. I was flying blind before that since
sets an environment variable to 1, and this is read by the cmake binaries.
Cheers,
Juan
Brandon Van Every wrote:
On 7/30/07, Juan Sanchez [EMAIL PROTECTED] wrote:
Thanks for the make VERBOSE=1. I was flying blind before that since
it wasn't on the man page.
It wasn't on the man page of your
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Is it possible to get the include paths from ADD_DIRECTORIES into a
custom command? I need to pass along the include path for a special
swig invocation.
Regards,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake
When I create a new cmake area, the tests are failing since it cannot
find the 64bit version of our tools on linux.
Is there anyway to pass the -B option to C and C++ compiler during the
compiler testing phase?
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
Is there any way to pass a flag to g++ being invoked by the testing
utils? I'm at least able to put the c++ compiler specification in a
cache file, but I need to know how to prevent the path to the linker
utils to be at the whim of the developer's environment.
Regards,
Juan
gga wrote:
Juan Sanchez
It looks like it should work.
Thanks,
Juan
Alexander Neundorf wrote:
On Wednesday 01 August 2007 18:53, Juan Sanchez wrote:
Is it possible to get the include paths from ADD_DIRECTORIES into a
custom command? I need to pass along the include path for a special
swig invocation.
Does
Hi Bill,
I was able to add CMAKE_CXX_FLAGS to my initial cache file and it
worked. Thanks for the clarification.
Thanks,
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
Hello gga,
Unfortunately, the ADD_DEFINITIONS aren't being used in the initial
tests being done by cmake. What I've found
I created a custom command to generate a cpp file.
I then use this cpp file to create a library as a separate add_library
command.
Whenever I type make, this cpp file is regenerated, and the library is
recreated. Compiling this file is super expensive. Nothing has changed
between invocations
I found the problem. The output from the custom command has to
explicitly specify the destination path of the output file.
OUTPUT ${PROJECT_BINARY_DIR}/output.cc
I was already specifying the full path for the input to the library.
Regards,
Juan
Juan Sanchez wrote:
I created a custom
able to compile and link a simple 'hello world!' program?
ld is the linker. On a redhat system it's in the binutils package. I
have no idea where it would be on ubuntu. It is independent of the
compiler.
Regards,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
In addition, if it is crt1.o which is missing, it is in glibc-devel on a
redhat 7.3 system.
Regards,
Juan
Juan Sanchez wrote:
Matthew Woehlke wrote:
Alex Dantart wrote:
Matthew Woehlke wrote:
Alex Dantart wrote:
.
.
.
Anyway, this line seems to be the important clue:
/usr/bin/ld: crt1
problem, but with a simple solution.
On debian:
apt-get install libc6-dev
On Fedora:
$ locate crt1.o
/usr/lib/crt1.o
On Ubuntu:
apt-get install libc6-dev
{ If not root, sudo apt-get install libc6-dev }
Juan Sanchez wrote:
In addition, if it is crt1.o which is missing, it is in glibc-devel
the source files instead of me specifying them?
Is there a better way of preventing rebuilds when I know that my changes
don't invalidate the object files I already have compiled?
Regards,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
Alexander Neundorf wrote:
On Thursday 09 August 2007 12:57, Juan Sanchez wrote:
I've been trying to find a good explanation of how the /fast target
works online? Is there a place where the exact behavior documented?
Also my concern is that adding a source file to CMakeLists.txt file
triggers
PROJECT(main)
SET (SRCS a.cc b.cc c.cc d.cc e.cc f.cc g.cc)
ADD_EXECUTABLE(a ${SRCS})
ADD_LIBRARY(b ${SRCS})
SET_SOURCE_FILES_PROPERTIES (
${SRCS}
COMPILE_FLAGS -Wall
)
Bill Hoffman wrote:
Juan Sanchez wrote:
I just added a source file to the list of sources in my library and now
}
COMPILE_FLAGS -Wall
)
I didn't test, but here the PROPERTIES keyword is missing. Is it just a
copy'n
paste error or does it still happen if you insert it ?
Alex
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake
I am having the following issue. I want to create both a libFOO.a and a
libFOO.so. Note that the libFOO.so is composed of more sources than the
libFOO.a.
I use OUTPUT_NAME in order so they have the same name. I can make the
FOOSTATIC, libFOO.a, target, just fine. However, making the
Hi Bill,
Thanks, it works when I do this in SET_TARGET_PROPERTIES.
Juan
Juan Sanchez wrote:
Hi Bill,
What's the proper syntax? Setting the variable in CMakeLists.txt doesn't
work. Neither does setting it in my initial Cache file (loaded with
cmake -C).
SET (CLEAN_DIRECT_OUTPUT 1 CACHE
Hi Bill,
What's the proper syntax? Setting the variable in CMakeLists.txt doesn't
work. Neither does setting it in my initial Cache file (loaded with
cmake -C).
SET (CLEAN_DIRECT_OUTPUT 1 CACHE STRING 1)
Thanks,
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
I am having the following issue
.
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
After some extensive googling, I found the solution here.
http://www.mail-archive.com/cmake@cmake.org/msg01890.html
Juan Sanchez wrote:
Hi,
On linux, I need to generate an shared library from an archive. I need
to have:
-Wl,-whole-archive
before and
-Wl,-no-whole-archive
? This FAQ entry is scaring some of my colleagues:
That means I have to build all my library objects twice, once for shared
and once for static. I don't like that!
and they are on the prowl for cmake dealbreakers.
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602
What would be the best way to tackle having dependencies with multiple
packages? For example, if package A depends on both packages B and C:
1. To make sure the compiler is the same
2. Know what flags where used for the sources in the dependency
3. Know whether or not the static archive is
think that it
is a valid approach. I'd prefer not to engage in wiki wars where I
replace the untrue statement, with a technically correct hack. Then
someone goes and changes it back.
Juan
Brandon Van Every wrote:
On 9/13/07, Juan Sanchez [EMAIL PROTECTED] wrote:
The FAQ doesn't mention the trick
, but requires that
Kitware freeze a public interface to the object file locations. I
don't know if they're willing to do that.
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan
extracted.
Even with Brandon's solution, I don't think ar let you add multiple .o
files of the same name in the archive. The symbols of the first .o file
will get replaced by the symbols of the second .o file to be added.
Juan
Goswin von Brederlow wrote:
Juan Sanchez [EMAIL PROTECTED] writes:
Hello
Hello Brandon,
How do you create the final archive without the ar command?
Juan
Brandon Van Every wrote:
On 9/18/07, Juan Sanchez [EMAIL PROTECTED] wrote:
Even with Brandon's solution, I don't think ar let you add multiple .o
files of the same name in the archive.
I'm going to guess you
.
Juan Sanchez wrote:
Hello Brandon,
How do you create the final archive without the ar command?
Juan
Brandon Van Every wrote:
On 9/18/07, Juan Sanchez [EMAIL PROTECTED] wrote:
Even with Brandon's solution, I don't think ar let you add multiple .o
files of the same name in the archive
It appears that the set command cannot override a variable specified as
a MACRO argument.
For example:
MACRO (ADD_GADB RCMD)
does not accept changes to RCMD within the macro using the set command.
Is there a way to override this?
Thanks,
Juan
___
I would argue that the following snippet of code should either print
CAT twice or die. Unfortunately it first prints DOG and then CAT.
Thanks,
Juan
MACRO(FOO BAR)
SET (BAR CAT)
MESSAGE(${BAR})
ENDMACRO(FOO)
FOO(DOG)
MESSAGE(${BAR})
Bill Hoffman wrote:
Juan Sanchez wrote:
What I
Ok,
But cpp doesn't discriminate between ${BAR} and BAR.
#include iostream
using namespace std;
#define foo(x) x = 3; cout x \n;
int main()
{
int y = 1;
foo(y);
cout y endl;
}
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
I would argue that the following snippet of code should
Hello,
How do you add an externally library for linking into a target? I am
getting something like this from TARGET_LINK_LIBRARIES?
CMake Error: Attempt to add link library /bar/linux-x86/opt/foo.a to
target waterlooApps which is not built by this project.
Thanks,
Juan
I want run a test program and pipe its results to a file. I then want
to compare this file to the golden results using diff.
Does anyone have a macro or cookbook example for doing this?
Thank you,
Juan
___
CMake mailing list
CMake@cmake.org
libraries. I always disable 80 bit extended precision on linux since
the results are non-deterministic with respect to compiler settings.
Regards,
Juan
Alan W. Irwin wrote:
On 2007-09-24 10:05-0500 Juan Sanchez wrote:
Hello Alan,
From your example, what in this statement that causes
.
Alin
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Awesome. I love that guys work on bibtex and bibtools.
Juan
Mathieu MARACHE wrote:
2007/9/25, Juan Sanchez [EMAIL PROTECTED]:
Hi Alan,
I also have floating point results I want to account for. I'm thinking
about writing a diff script for numerical results which uses an absolute
, is ever activated.
fixed_fmt^[cC*dD].*\n { return EOSTMT; } /* empty lines */
Do you have any info about how to make submissions and getting the
latest CVS?
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
It turns out that any word of the word Use or use as a word anywhere in
a comment causes
Anyone know what are the valid comment lines in all the Fortran variants?
I know of lines beginning with c, C, or * in the first column.
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
Hi Bill,
I wouldn't mind taking a stab at it.
It would be easy enough to tell lex to drop any line starting
what is going on here or how
to fix it?
Thanks,
Justin
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
tests...
Start processing tests
Test project /home/juans/bar
1/ 1 Testing foo Passed
Juan Sanchez wrote:
Would you happen to have a file named test in your binary area? Make
will see the file and think that the target test is up to date.
A proper gnu makefile would
naturally).
Marking the test target as phony in the Makefile resolved the issue.
It sounds like this should be fixed in the Makefile generator. There are
several other targets that should be marked as phony as well.
Thanks,
Justin
On Wednesday 26 September 2007 09:43:42 Juan Sanchez
How do I get the INCLUDE_DIRECTORIES path? I need to feed into into the
search path for the swig command line.
Thanks,
Juan
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
I am using ADD_CUSTOM_COMMAND to produce an output.
Unfortunately, if the commands in it fail, the OUTPUT. Hence the OUTPUT
is up to date, even though it is invalid. Is there a way to tell
ADD_CUSTOM_COMMAND to remove its output when it fails?
Thanks,
Juan
the files
created by cmake to be in this directory so I could clean up my
directory more easily )
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512
Marie-Christine Vallet wrote:
Juan Sanchez wrote:
Could this be an issue with linker order? Most linkers are one pass.
The library containing the undefined references should be on the linker
line before the library containing the symbols, or vice-versa (I keep
forgetting).
The symbols
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http
I just discovered that the moment I add a second SET_TARGET_PROPERTIES
statement for a specific target, cmake will implicitly fail, and not
write out a Makefile. It even states that it is writing the build
files, but it does not.
This is cmake 2.4.7 on linux.
Any advice?
Juan
to
the list? Or, if not, could you post your source as is?
On 10/2/07, Juan Sanchez [EMAIL PROTECTED] wrote:
I just discovered that the moment I add a second SET_TARGET_PROPERTIES
statement for a specific target, cmake will implicitly fail, and not
write out a Makefile. It even states
`
WORKING_DIRECTORY ${PROJECT_BINARY_DIR}
COMMAND echo `pwd`
WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
)
ADD_CUSTOM_TARGET( zed ALL DEPENDS bar)
Will always print the source directory.
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
How can you ensure that an install has done before you attempt to run
the tests?
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
the
arguments given.
Please let me know what I need to do to get this to run.
Testing/Temporary/LastTest.log
always appears to be empty and the -VV option does not work.
This is cmake 2.4.7.
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
and make my executable depend on that new library target.
Thanks, Tal
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan
-0500 Juan Sanchez wrote:
Hi,
I'm trying to run the following test:
ADD_TEST(foo ${CMAKE_TEST_COMMAND} --build-run-dir
${PROJECT_SOURCE_DIR} -VV --test-command ls -ltar /tmp)
But it doesn't seem to be running correctly. It needs to be run from
${PROJECT_SOURCE_DIR}, and the test command
Juan Sanchez wrote:
I am trying to follow an example that is in the cmake book. It is in
section 8.5 Using CTest to Drive Complex Tests on page 109. While my
example differs in that it doesn't use all the arguments being used in
the book's example, it is very important that I understand how
, is there
any way to tell ctest to run in a specific directory?
Thanks,
Juan
Juan Sanchez wrote:
To solve my issue, I only need to specify the following. Otherwise, no
error is printed, the test will always past, and ctest --debug prints
pages and pages of debug info.
ENABLE_TESTING()
ADD_TEST(foo
://www.cmake.org/mailman/listinfo/cmake
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake
]$
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext
The test scripts for an existing project rely greatly on the installed
directory structure. Is it possible to always force an install before
the tests are run?
Thanks,
Juan
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
In this example, the target name foo has a different OUTPUT_NAME. How
do I tell ADD_CUSTOM_COMMAND to use the real name of the target when I
try to use the copy command within?
ADD_CUSTOM_COMMAND(TARGET foo POST_BUILD COMMAND ${CMAKE_COMMAND} -E
copy foo ${PROJECT_SOURCE_DIR}/${INSTALL_DIR})
in the correct place?
Regards,
Juan
Alan W. Irwin wrote:
On 2007-10-09 10:12-0500 Juan Sanchez wrote:
The test scripts for an existing project rely greatly on the installed
directory structure.
For your information, that's contrary to the fundamental idea behind ctest
(and autotools
Since I must copy a target after it's built, I synthesize a compile time
install command.
Unfortunately, the copy command obliterates the destination directory
with a copy of the file being created.
This seems to be contrary to the cmake -E help documentation:
copy file destination - copy file
I apologize. Upon further testing, this doesn't appear to be an issue.
Thanks,
Juan
Juan Sanchez wrote:
Since I must copy a target after it's built, I synthesize a compile time
install command.
Unfortunately, the copy command obliterates the destination directory
with a copy of the file
Hello,
Is it possible to build both purify and non purify targets by changing
CMAKE_CXX_LINK_EXECUTABLE? Unfortunately the following example purify's
both binaries.
ADD_EXECUTABLE(hello helloworld.cc)
SET (CMAKE_CXX_LINK_EXECUTABLE purify -cache-dir=/tmp
${CMAKE_CXX_LINK_EXECUTABLE})
To clarify my question, should I expect changing
CMAKE_CXX_LINK_EXECUTABLE to apply to both targets in the example below?
This is cmake 2.4.7.
Regards,
Juan
Juan Sanchez wrote:
Hello,
Is it possible to build both purify and non purify targets by changing
CMAKE_CXX_LINK_EXECUTABLE
Someone in my group is investigating dejagnu. I was wondering if anyone
with experience in ctest and dejagnu has any thoughts on these two
testing systems?
Thanks,
Juan
___
CMake mailing list
CMake@cmake.org
earlier, for some
reason this seems to just be a non-issue in 2.4.7.
Thanks everyone for the help.
- Christian
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext
Where is the source for wxCMakeSetup?
What platforms do you need it to compile for? I could do linux and
maybe cygwin.
Juan
Mike Jackson wrote:
I am more intersted in a nice Qt CMakeSetup but with some more added
features. wxWidgets and Fltk just do not look that good under OS X. I
am
With wxWidgets 2.6.8, the 64 bit issues appear to be solved.
Unfortunately, it no longer likes receiving (const char *)'s without
converting them using some special functions. It would take a while to
change the code according to the instructions in:
Brandon Van Every wrote:
On Nov 2, 2007 11:49 AM, Juan E. Sanchez [EMAIL PROTECTED] wrote:
On Fri, 2 Nov 2007, Brandon Van Every wrote:
To make real improvements in all of those areas, you'd need a lot of
funding. What kind of mandate do you have? There's not much point in
saying
://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Oh,
I guess you did. My apologies.
I guess the best way to fix your issue would be to move to a lua frontend.
Juan
Brandon Van Every wrote:
On Nov 2, 2007 4:22 PM, Juan Sanchez [EMAIL PROTECTED] wrote:
My suggestion as a temporary work around would be to apply a namespace
prefix
://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
.
Regards,
Juan
Juan Sanchez wrote:
Two things with convenience libraries. Part of this may be in the FAQ:
On linux, compile the code fPIC or fpic (slightly different meanings).
So for library hello:
SET_TARGET_PROPERTIES(
hello PROPERTIES
OUTPUT_NAME hello
CLEAN_DIRECT_OUTPUT 1
.
So far I have fixed the issue by linking one of the libs of
libfoo.so (say libx.a) to libbar.so. But this smells of nasy
workaround.
Obviously I'm doing something wrong here, so could anyone please help?
Thanks!
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
COMPILE_FLAGS -fPIC
)
SET_TARGET_PROPERTIES(
zzDYNAMIC PROPERTIES
OUTPUT_NAME zz
CLEAN_DIRECT_OUTPUT 1
)
ENDIF(CMAKE_SYSTEM_NAME STREQUAL Linux AND CMAKE_COMPILER_IS_GNUCC)
Regards,
Juan
Juan Sanchez wrote:
Hello,
There a much nicer platform independent writeup
I was reading exactly the link you sent, and the same one you accused
Brandon of not reading. If there were supplemental materials, you
should have sent them. I am not a lawyer.
To be honest, the only compelling languages I've seen so far in this
discussion is lua and tcl. This is because they
?
#if 0
#include foo.h
#endif
HS
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake
.
If that doesn't work, try SET_TARGET_PROPERTIES with the LINK_FLAGS you
want.
Juan
Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
they are preparing a new edition of the book.
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450 Ext. 54395
512-602-4395
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
If I remember the original intent, I thought the desire was to enforce
some draconian indenting policy.
Shouldn't that be a script in your source code management tool? For
example, the indentation policy will be enforced the moment the file is
checked in.
Juan
Eric Noulard wrote:
2007/11/15,
Eric Noulard wrote:
2007/11/16, Juan Sanchez [EMAIL PROTECTED]:
If I remember the original intent, I thought the desire was to enforce
some draconian indenting policy.
Draconian :=)
Not really I'll consider this homogeneous in order
to avoid stupid editor configuration config spurious
James Bigler wrote:
Eric Noulard wrote:
2007/11/16, Juan Sanchez [EMAIL PROTECTED]:
Shouldn't that be a script in your source code management tool? For
example, the indentation policy will be enforced the moment the
file is
checked in.
Yes your are damn right, and I did this in the past
?
cm_add_library{simpleLib STATIC simpleLib.cxx simpleCLib.c simpleWe.cpp}
Regards,
Juan
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
--
Juan Sanchez
[EMAIL PROTECTED]
800-538-8450
Alexander Neundorf wrote:
On Tuesday 27 November 2007, Juan Sanchez wrote:
...
How about?
cm_add_library{simpleLib STATIC simpleLib.cxx simpleCLib.c simpleWe.cpp}
Are you sure putting it all in one quoted string will make getting the
quoting
right simpler than it is now ?
Please
Brandon Van Every wrote:
On Nov 27, 2007 3:22 PM, Juan Sanchez [EMAIL PROTECTED] wrote:
How about?
cm_add_library{simpleLib STATIC simpleLib.cxx simpleCLib.c simpleWe.cpp}
That paradigm is crippled with respect to FOREACH and LIST style
processing. I can't really see everyone on the CMake
I'm evaluating CMAKE for use by our group and I am running into an issue
with selecting the compiler.
Is there any way to set the compiler and flags in the CMakeLists.txt
file? This information appears to be ignored. The FAQ as well as the
book suggest setting environment variables.
We have a
Bill Hoffman wrote:
Juan Sanchez wrote:
I'm evaluating CMAKE for use by our group and I am running into an issue
with selecting the compiler.
Is there any way to set the compiler and flags in the CMakeLists.txt
file? This information appears to be ignored. The FAQ as well as the
book
macros tests honored when determining the dependencies?
Are the macro defines used in the compilation also passed along to the
dependency checker for each build variant?
Thanks,
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
Hi Bill,
We are going to require the developer to run a specific
? Then it would be possible for developer's existing
Makefiles to not get clobbered by cmake. Gnu make could then be called
with the -f specification for the Makefile name.
Thanks,
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
So, what is the current build system and how does it work?
Everyone
suggestion.
>
>
>
> --
>
> J. Adam Stephens, Ph.D.
>
> Dakota Support Analyst
>
> https://dakota.sandia.gov/
>
> Optimization and UQ
>
> Sandia National Laboratories
>
> Albuquerque, NM
>
>
>
>
>
> *From: *Juan Sanchez
> *Date: *Tue
Hello,
Are you able to use BUILD_WITH_INSTALL_RPATH:
https://cmake.org/cmake/help/v3.13/prop_tgt/BUILD_WITH_INSTALL_RPATH.html
https://cmake.org/cmake/help/v3.13/prop_tgt/INSTALL_RPATH.html#prop_tgt:INSTALL_RPATH
Regards,
Juan
On Tue, Feb 5, 2019 at 4:00 PM Stephens, J. Adam via CMake
wrote:
Hello,
https://stackoverflow.com/questions/1417957/show-just-the-current-branch-in-git
suggests:
git rev-parse --abbrev-ref HEAD
Regards,
Juan
On Sat, Jun 8, 2019 at 5:25 PM Steven Truppe wrote:
> Hi everyone,
>
> i want to have code lines like:
>
> #define BUILD_VERSION
>
> and the
On Wed, May 22, 2019 at 10:27 AM Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> Do this all the time both for our CDash nightlies and when I am developing
> on Windows. The essential pieces of the puzzle are the following:
>
> 1: Ninja needs to be on your path
> 2: The compilers need to
1 - 100 of 109 matches
Mail list logo