The first time you need to checkout next, you should do:
git checkout -b next origin/next
which will set it up as a local branch that tracks the remote
'origin/next' branch...
On Mon, Jun 14, 2010 at 1:10 PM, Mathieu Malaterre
mathieu.malate...@gmail.com wrote:
Hi there,
I discover that
David Cole wrote:
The first time you need to checkout next, you should do:
git checkout -b next origin/next
which will set it up as a local branch that tracks the remote
'origin/next' branch...
This is mentioned in the tutorial
Michael,
thanks for the feedback. Following the advice given, I've modified the project
so that it generates an hdf5-config.cmake file, which checks for If(NOT target
blah blah) and then loads the hdf5-targets.cmake file.
All seem to be clean and tidy.
I had one small problem which was
Hi again,
Am Sonntag, 13. Juni 2010 schrieb Michael Hertling:
SET(var1 ${var1} PARENT_SCOPE)
Thank you; that completey solved it!
Thanks again,
C.M.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
I need to provide easy adding for source files to the developers,
So it would be nice to just have a CMakelists.txt in every
subfolder,
which then edits the source-variable.
Also consider to use properties for such a purpose.
Which property do you actually think about?
Regards,
Put the scripts in the cmake wiki and put it into the public domain.
Easiest for all.
-
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Jun 13, 2010, at 16:33, Andreations
On 6/14/2010 8:31 AM, Mike Jackson wrote:
Put the scripts in the cmake wiki and put it into the public domain.
Easiest for all.
To be compatible with CMake, I would say a BSD license would be the
best. gitorious might be a good starting place. We tried the converter
here, and it created
make test VERBOSE=1
or even better,
ctest -VV
Ryan
On 06/14/2010 09:47 AM, Felipe Sodré Silva wrote:
Hello all,
Is there a way to see the command lines used for running the tests
when I do a make test on linux?
Thanks !
___
Powered by
On Mon, Jun 14, 2010 at 01:40:38PM +0200, Aeschbacher, Fabrice wrote:
I need to provide easy adding for source files to the developers,
So it would be nice to just have a CMakelists.txt in every
subfolder,
which then edits the source-variable.
Also consider to use properties for
On 6/14/2010 10:59 AM, Ryan Pavlik wrote:
make test VERBOSE=1
or even better,
ctest -VV
Ryan
make test ARGS=-V
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Hi,
I'm currently using
CREATE_TEST_SOURCELIST(Tests ${KIT}CxxTests.cxx
${TestSourceFiles}
EXTRA_INCLUDE header1.h
EXTRA_INCLUDE header2.h
)
to genereate a test executable. I'd like to replace this with a call
something like
CREATE_TEST_SOURCELIST(Tests ${KIT}CxxTests.cxx
I am happy to announce that CMake 2.8.2 has entered the release
candidate stage! You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
Following is the list of changes in this release. (If you notice
something missing please let me know and I will add it to the official
On 2010-06-14 11:24-0400 David Cole wrote:
I am happy to announce that CMake 2.8.2 has entered the release
candidate stage! You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
Following is the list of changes in this release. (If you notice
something missing please let
Hi there,
I reported a bug a couple of month back, which apparently was fixed with Closing
this since the new TARGET option for CTEST_BUILD is well documented.
I am looking at the git web interface of ctest_build:
On 6/14/2010 12:38 PM, Alan W. Irwin wrote:
On 2010-06-14 11:24-0400 David Cole wrote:
I am happy to announce that CMake 2.8.2 has entered the release
candidate stage! You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
Following is the list of changes in this
On 2010-06-14 12:58-0400 Bill Hoffman wrote:
The patch mentioned there is necessary for the Wine platform and presumably
has been substantially tested in the two months since you made that change.
That change is in the release, just not mentioned.
Good. That should make it much easier for
On 6/14/2010 1:39 PM, Alan W. Irwin wrote:
On 2010-06-14 12:58-0400 Bill Hoffman wrote:
The patch mentioned there is necessary for the Wine platform and
presumably
has been substantially tested in the two months since you made that
change.
That change is in the release, just not mentioned.
I have a question about building a project with static libraries. If you have a
set up like the following will the final static library be the only thing that
you install? I found that there was still unresolved external symbols when I
only linked against Fruit.lib in the test program.
No, you need to install them all: a static library only contains
basically the object files of the specified sources, archived together.
Auto* and libtool do some (unpleasant) magic to split and re-combine
these archives, in some cases, and this is a common question on this
list. If you want
Bad things happening... I have existing builds that I have run... I
have been buliding with Mingw. If I do 'cmake-gui .' in the target
build directory, then the generator pops up and says it is generating
MingW Makefiles. But if I then type 'make' it says
M:\build\mingw\sackmake
-- Building
http://www.cmake.org/Bug/view.php?id=10388
0877-Update-watcom-support.patch (not the first patch, which I can't
find a way to delete to avoid confusion)
Oh and checking the other bug submission, I didn't provide required
feedback to define why addtional cflag types would be of use.
In your Unification Script, you have the following:
# I found that SUBDIRS had a more desirable behavior for me as
to where
# binaries were created as opposed to ADD_SUBDIRECTORY.
SUBDIRS(lua luasocket luafilesystem luasql lualogging luadoc)
I was wondering if you could
I would suggest you re-open that bug, since clearly that option is NOT
documented at all.
It's not mentioned on
http://www.cmake.org/cmake/help/ctest-2-8-docs.html#command:ctest_build ,
nor in the output of ctest --help-command ctest_build.
It IS mentioned in at least one Kitware Quarterly
On 06/14/2010 12:09 PM, Biddiscombe, John A. wrote:
Michael,
thanks for the feedback. Following the advice given, I've modified the
project so that it generates an hdf5-config.cmake file, which checks for
If(NOT target blah blah) and then loads the hdf5-targets.cmake file.
This seems to
What bug are you referring to?
On Mon, Jun 14, 2010 at 12:58 PM, mathieu.malate...@gmail.com wrote:
Hi there,
I reported a bug a couple of month back, which apparently was fixed with
Closing this since the new TARGET option for CTEST_BUILD is well
documented.
I am looking at the git
Never mind. I just read the subject line
You mean this one, right?
http://public.kitware.com/Bug/view.php?id=9835
On Mon, Jun 14, 2010 at 8:17 PM, David Cole david.c...@kitware.com wrote:
What bug are you referring to?
On Mon, Jun 14, 2010 at 12:58 PM, mathieu.malate...@gmail.com
On 6/14/2010 6:59 PM, J Decker wrote:
Bad things happening... I have existing builds that I have run... I
have been buliding with Mingw. If I do 'cmake-gui .' in the target
build directory, then the generator pops up and says it is generating
MingW Makefiles. But if I then type 'make' it says
I will try some more, I ran 'cmake-gui .' and checked the generator,
and clicked cnofigure and generate there, expecting that might have
cleaned it. then I ran cmake, and it detected my visual studio
enviornment and started using it.
Okay, what might have happened, I had some shells open that
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via bd032940e0f403dfbce37b5356e1be5b5704fecc (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 229a4d454a05e377f014c9ca4a21da26d91a2ac0 (commit)
via
30 matches
Mail list logo
