On 01/12/2011 03:03 PM, Alexey Livshits wrote:
>> Thing is, you can't *rely* on DESTDIR *not* being used by the user of
>> your project. If a user shoots himself in the foot, that's his fault,
>> but when designing your test architecture you IMHO shouldn't make the
>> use of DESTDIR impossible. I'm
> Thing is, you can't *rely* on DESTDIR *not* being used by the user of
> your project. If a user shoots himself in the foot, that's his fault,
> but when designing your test architecture you IMHO shouldn't make the
> use of DESTDIR impossible. I'm sure Debian/Ubuntu/the/whole/zoo would
> object to
On 01/12/2011 02:47 PM, David Cole wrote:
> On Wed, Jan 12, 2011 at 8:34 AM, Alexey Livshits wrote:
>
>>> Well, if you don't want any help fixing the real problem, then the
>>> answer is simple: CMake can't possibly give you that information because
>>> of DESTDIR.
>>
>> Thank you.
>>
>>> So, go
> Why can't you just set CMAKE_INSTALL_PREFIX to some path that you know and
> then reference that from your tests that run the installed version?
I thought about it, but I'd like to keep it independent of some known
path. If you mean, there is no other way, I should give them a try.
> DESTDIR wi
On Wed, Jan 12, 2011 at 8:34 AM, Alexey Livshits wrote:
> > Well, if you don't want any help fixing the real problem, then the
> > answer is simple: CMake can't possibly give you that information because
> > of DESTDIR.
>
> Thank you.
>
> > So, go and fix your project.
>
> I wish I could, but its
> Well, if you don't want any help fixing the real problem, then the
> answer is simple: CMake can't possibly give you that information because
> of DESTDIR.
Thank you.
> So, go and fix your project.
I wish I could, but its not so simple. If you have an idea, just let me know.
--
BG,
Alexey
__
On 01/12/2011 02:16 PM, Alexey Livshits wrote:
> As I mentioned above, there are targets foo1 and foo2, build from foo
> sources, and the output name has to be foo. This is the conflict. The
> test depends from foo1 and bar2.
>
>> If you don't explain the problem more clearly, people won't be able
As I mentioned above, there are targets foo1 and foo2, build from foo
sources, and the output name has to be foo. This is the conflict. The
test depends from foo1 and bar2.
> If you don't explain the problem more clearly, people won't be able to
> help you; particularly because I suspect that you
> If the two "version" are needed you may build them in a single build.
>...
> but may be I'm missing something about your "2 versions"?
That's what I already do. The problem is, libv1 and libv2 should be
called libv.
> Alternatively, may be you can decide that your needed
> "temporary" install wi
On 01/12/2011 01:48 PM, Alexey Livshits wrote:
>> Yes, make the tests run without installation. To give more advice, we'd
>> need to know more about those "dependencies". Are they other
>> executables? Data files? Libraries?
>
> Well, if I could do that, I wouldn't ask ;)
> I have 2 versions, whic
2011/1/12 Alexey Livshits :
>> Yes, make the tests run without installation. To give more advice, we'd
>> need to know more about those "dependencies". Are they other
>> executables? Data files? Libraries?
>
> Well, if I could do that, I wouldn't ask ;)
> I have 2 versions, which are built from the
> Yes, make the tests run without installation. To give more advice, we'd
> need to know more about those "dependencies". Are they other
> executables? Data files? Libraries?
Well, if I could do that, I wouldn't ask ;)
I have 2 versions, which are built from the same sources. So I have to
have 2 d
On 01/12/2011 01:24 PM, Alexey Livshits wrote:
>> What do you want to do?
>
> I have some tests, which cannot be run without installation because of
> dependencies. So I need to specify the install path to add_test. Is
> there a better approach?
>
Yes, make the tests run without installation. To
> What do you want to do?
I have some tests, which cannot be run without installation because of
dependencies. So I need to specify the install path to add_test. Is
there a better approach?
--
BG,
Alexey
___
Powered by www.kitware.com
Visit other Kitw
2011/1/12 Alexey Livshits :
> Hello,
> how can I determine the path to installed target?
When ?
If it is inside a CMakeLists.txt i.e. at CMake time usually you can't
unless you specify absolute install path in your install rules.
> The problem is, if I
> set DESTDIR for example "D:\", I the insta
Hello,
how can I determine the path to installed target? The problem is, if I
set DESTDIR for example "D:\", I the install path becomes
"D:\Programme\", so I cannot use DESTDIR to determine
the path.
--
BG,
Alexey
___
Powered by www.kitware.com
Visit o
16 matches
Mail list logo
