David Abrahams wrote:
Another new feature in CTest/CDash development heads which may be of interest
to Boost is support for subproject labeling. See their main dashboard page here:
http://trilinos-dev.sandia.gov/cdash/index.php?project=Trilinos&date=2009-02-27
Functionally, it's pretty dar
I just saw that. Fixed. Thanks.
-t
Kito Berg-Taylor wrote:
In the current svn version of boost there appears to be a mistake in the
root CMakeLists.txt file. There is an errant "c" on line 51. Patch
included below. (Ironic location for a bug :-P)
Index: CMakeLists.txt
===
In the current svn version of boost there appears to be a mistake in the
root CMakeLists.txt file. There is an errant "c" on line 51. Patch
included below. (Ironic location for a bug :-P)
Index: CMakeLists.txt
===
--- CMakeLists.txt
Randy Heiland wrote:
Hmm. So setting those manually in your cmake cache triggers a reconf
for boost-cmake, but not the other project you speak of?
-t
Correct.
I think I asked the wrong question if you edit your CMakeCache.txt
for any reason the makefiles will get regenerated. I jus
On Mar 4, 2009, at 10:15 AM, troy d. straszheim wrote:
Randy Heiland wrote:
Hello,
I'll post this in case someone knows the answer, while I go
searching...
I want to specify a non-system Python to be used, so I set the
following
in my CMakeCache.txt (obviously, I'm on OSX):
PYTHON_DEB
Randy Heiland wrote:
Hello,
I'll post this in case someone knows the answer, while I go searching...
I want to specify a non-system Python to be used, so I set the following
in my CMakeCache.txt (obviously, I'm on OSX):
PYTHON_DEBUG_LIBRARY:FILEPATH=/Python.framework
PYTHON_EXECUTABLE:FILEPA
Hello,
I'll post this in case someone knows the answer, while I go searching...
I want to specify a non-system Python to be used, so I set the
following in my CMakeCache.txt (obviously, I'm on OSX):
PYTHON_DEBUG_LIBRARY:FILEPATH=/Python.framework
PYTHON_EXECUTABLE:FILEPATH=/usr/local/bin/pyt
I know... I miss unix for this, anyway if I uncheck every modularizing
project for the building ("-modularize") the headers of
are not erased. This seems work, but the problem is that
every time that you rebuild, cmake's generation is launched again and so
while a rebuilding is performed, Visual C
Trimoldi, F. (Filippo) wrote:
Yes, in fact in the default configuration of my solution, both "INSTALL"
and "modularize" projects aren't checked for their building, but a the
end of my first building all my headers are erased... what I'm making a
mistake in?
I don't know. Unfortunately, I don'
Yes, in fact in the default configuration of my solution, both "INSTALL"
and "modularize" projects aren't checked for their building, but a the
end of my first building all my headers are erased... what I'm making a
mistake in?
-Original Message-
From: boost-cmake-boun...@lists.boost.org
[
10 matches
Mail list logo