script that invokes the Google
protobuf generator). Unfortunately, there aren't very many decent IDEs that
can handle more than one source language or custom build targets.
--
-- Talin
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.
ve my problems, but at the moment I'm stuck with the version
that Ubuntu distributes.
In any case, I've been struggling with this specific problem off and on for
over 3 years, asking for help on various forums, and I've never found an
answer that actually works for me.
--
-- Talin
_
hat I did:
The dependency file generator creates a dependency entry for each target in
the library:
set(TART_TESTING_ASSERTS_DEPS
"/home/talin/Projects/tart/trunk/stdlib/tart/core/AssertionFailureException.tart"
"/home/talin/Projects/tart/trunk/stdlib/tart/core/Debug.tart&q
9 at 11:21 AM, Alan W. Irwin
wrote:
> On 2009-12-30 10:42-0800 Talin wrote:
>
> I guess what I am asking is - if I modified my build script to generate a
>> text file (Makefile, CMakeLists.txt or whatever) containing the
>> dependencies, would CMake be able to use it? I
(although it is rather complex and clumsy), I wonder if CMake can support
something similar?
2009/12/30 Alexander Neundorf
> On Wednesday 30 December 2009, Talin wrote:
> > What's the recommended way in CMake to do automated dependency generation
> > for languages that aren't di
Lists.txt for the two libraries.
I've tried putting $PROJECT_BINARY_DIR and $CMAKE_BINARY_DIR in front of
testing.lib, neither of which seems to make any difference. I've also tried
depending on the actual build product (testing.lib.bc) rather than the
abstract target testing.lib. Stil
tract this
information. Is there some way I can get CMake to use this information in
subsequent builds?
--
-- Talin
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep message
