On 2014.03.19, at 07:21, Micha Hergarden wrote:
Hi, thanks for answering. Could you please elaborate a little?
> ExternalProject_Add has a DEPENDS option. What you can do is let X
> depend on Y
DEPENDS seems to mean that the external project depends on something
else. If I wanted to make X depen
Apparently NSIS 2.15 lacks a "v" in the version output string, which
causes the regular expression used in cmCPackNSISGenerator [0] to
fail.
The "v" was added back to the version string in 2.16 [1], and
presumably exists all the way through NSIS version 2.46.
[0]
https://github.com/Kitware/CMake
On both Windows 7 and Windows XP makensis.exe /VERSION seems to exit
normally, but it must be a bad return value or regex failure:
https://github.com/Kitware/CMake/blob/master/Source/CPack/cmCPackNSISGenerator.cxx#L437
--
Powered by www.kitware.com
Please keep messages on-topic and check the CM
That's one "workaround". Two more come to mind:
(1) Another would be to force the configure/build steps of an external
project to run *always* rather than when the stamp file indicates they
are out of date. You could take a look at the open chemistry super
build to see an example.
Specifical
Ok, so the only "workaround" to archive this is to use "file(GLOB_RECURS...)"
and rebuild the changed external project. Right?
Best Regards
> Am 19.03.2014 um 12:44 schrieb David Cole :
>
> Well, that sounds like the perfect way to use ExternalProject.
>
> But why do you want to show the sourc
Well, that sounds like the perfect way to use ExternalProject.
But why do you want to show the sources in Visual Studio? Just for ease
of looking at them?
As I said in my earlier reply... even if we showed the sources, editing
them would not trigger a rebuild of the external project. The
dep
Thanks, that worked like a charm :).
Kind regards,
Geert
2014-03-19 11:48 GMT+01:00 Nils Gladitz :
> On 19.03.2014 10:56, Geert Litjens wrote:
>
>>
>> Since this week I have been using BundleUtilities to automatically copy
>> third-party dependencies to the install directory. However, I have o
On 19.03.2014 10:56, Geert Litjens wrote:
Since this week I have been using BundleUtilities to automatically
copy third-party dependencies to the install directory. However, I
have one issue: when we make debug builds we use DEBUG_POSTFIX to
append _d to our executables and libraries (so we c
Dear all,
Since this week I have been using BundleUtilities to automatically copy
third-party dependencies to the install directory. However, I have one
issue: when we make debug builds we use DEBUG_POSTFIX to append _d to our
executables and libraries (so we can package both). However, as far as
Is it possible to hide some of the pages used in PackageMaker? For example if I
don't want to show the license dialog.
Best Regards
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to s
Because the external projects depends on different library versions than the
"SuperProject". Maybe I misconfigured something, but i don't know an
alternative.
E.g.: super project (AA) builds with version 9 of library X.
The external project B requires version 5 of library X and had some source
11 matches
Mail list logo
