Hello again,
CTEST_UPDATE_COMMAND is set to ${GIT_EXECUTABLE}.
I also tried to extend the CTEST_CHECKOUT_COMMAND variable, but here I get also
an error.
Please, could someone help?
Thanks in advance
Am 25.02.2013 um 18:15 schrieb NoRulez :
> Hello,
> i've set CTEST_UPDATE_OPTIONS as followe
On Sunday 24 February 2013, Chris Stankevitz wrote:
> On Sun, Feb 24, 2013 at 12:37 PM, Alexander Neundorf
>
> wrote:
> >> github links:
> >> https://github.com/chrisstankevitz/hello
> >> https://github.com/chrisstankevitz/hello-client
> >
> > Maybe we'll start with the old way and get to the ne
Hello,
i've set CTEST_UPDATE_OPTIONS as followed:
set(CTEST_UPDATE_OPTIONS "--tags")
I set this, because I need newely created and/or modified tags.
When I set this option then I get the error:
"git.cmd" "fetch" "--tags" Update command failed
Is there an other way of doing so?
Thanks in advan
Shall I force the compiler?
This is all I can find on the "CMake Cross Compiling" wiki: "If your
compiler is not able to build a simple program by default without special
flags or files (e.g. linker scripts or memory layout files), the toolchain
file as shown above doesn't work. Then you have to *
Martin Koller wrote:
> On Saturday 23 February 2013 14:58:11 Rolf Eike Beer wrote:
> > Martin Koller wrote:
> > > On Friday 22 February 2013 12:23:23 Koller, Martin wrote:
> > > > I propose the attached patch for CMakeDetermineSystem.cmake
> > > > Can someone add this to the mentioned mantis bug en
Surely I can refactor code to avoid cross-dependencies...
But the problem is more on the definition of the target link line at
executable level than on cross dependency.
Indeed even if C does not depends on B, or in your example X, writing
TARGET_LINK_LIBRARIES(EX1 libD libX1)
would always leads t
I see. I would not try to express this complexity to cmake. Is there a way you
can separate the alternate functionality out of C so that it doesn't cause the
dependency graph to fragment this way? Usually circular dependencies mean you
need to refactor something anyway. If you can make the dep g
Hi everyone,
Reading answer from leif and andreas, leads me to advance a bit.
To my opinion writing target_link_libraries(exe1 libB libC) would certainly
works (but I m not able to test it at the moment).
But my problem should be explain the more tricky way :
libB depends on libC function implem
Hello Pierre,
self reply as a correction, sorry:
what I meant was that only linking the executables
TARGET_LINK_LIBRARIES(EX1 libB libC1)
TARGET_LINK_LIBRARIES(EX2 libB libC2)
should suffice.
Andreas
Am 25.02.2013 um 14:14 schrieb Andreas Stahl:
> Hello Pierre,
>
> my knowledge concerning the
I think you shouldn't make B depend on anything, and just make sure that you
list all the libs you need at executable link time.
Sent from my iPhone
On Feb 25, 2013, at 7:47, Pierre Mallard wrote:
> Well it is indeed possible and it works... Note that static libraries 's
> object files are b
Hello Pierre,
my knowledge concerning the linking process is rather limited, but wouldn't
that mean you don't need to inter-link the libraries at all, when the symbols
are resolved at link-time with the executable?
add_executable(ex1 libB libC1 libC2) should suffice then.
Best regards,
Andreas
Well it is indeed possible and it works... Note that static libraries 's
object files are built with unresolved symbols. Final resolution is
performed when building executable
Therefore libB can compile without libC and conversely ...
Anyone else ?
On Mon, Feb 25, 2013 at 12:23 PM, Ansis Māliņš
>libB depends on libC and libC depends on libB.
How is that even possible? You compile B and it fails because there's no C
yet. You compile C and it fails because there's no B yet.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensou
Hello everyone,
This is certainly a known issue but I coulnd't find anything related to
this needs on internet :
I got :
an executable EX, a static library B and a static library C with cross
dependencies :
libB depends on libC and libC depends on libB.
EX depends on libB
If I write :
TARGET_LIN
David Brown wrote:
> I'm trying to patch and build a Makefile-based project using the
> ExternalProject module. My patch command looks like this:
>
> PATCH_COMMAND "patch -p1 -t -N <
> ${CMAKE_CURRENT_SOURCE_DIR}/IntelDFP.patch"
>
> When building, however, I get this:
>
> [ 10%] Performi
Am Sonntag, 24. Februar 2013 um 19:58:53, schrieb David Brown
> I'm trying to patch and build a Makefile-based project using the
> ExternalProject module. My patch command looks like this:
>
> PATCH_COMMAND "patch -p1 -t -N <
> ${CMAKE_CURRENT_SOURCE_DIR}/IntelDFP.patch"
>
> When building,
16 matches
Mail list logo
