n this way the shared libs would be found in the executable
directory first and any other "wrong" paths would not hurt.
Many thanks and regards,
Cornelis Bockemühl
--
Powered by kitware.com/cmake
Kitware offers various services to support the CMake community. For more
information on
stall" (but now I know at least when and why!). And the only way around - if
I want to avoid the configure_file solution - would be to do some proper
install(FILES...) instead - together with a little hacking regarding what the
right files actually are.
Best regards, Cornelis
--
Powered
is what I learned: doing the transfer with install() instead of a
file copy through configure_file gives me not only the more abstract level of
project organization, but also takes care of the RPATH...
Best regards,
Cornelis
Am Dienstag, Oktober 08, 2019 14:07 CEST, cornelis
schrieb:
Thanks for tha
copying the libs
- to a specific location where the plugin finding procedure finds them!
Regards, Cornelis
>
> On 08.10.2019 at 13:10, Eric Noulardwrote:
>
>
>
>
>
>
>
> Le mar. 8 oct. 2019 à 12:52, Co
mple" install directory tree
2) add some RPATH or RUNPATH setting to all the binaries that need it
Regards, Cornelis
--
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 su
The missing link to my "cmake teacher web page":
https://pabloariasal.github.io/2018/02/19/its-time-to-do-cmake-right/
Regards, Cornelis
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offe
> I think that the word install is used consistently between GNU autotools and
> CMake:
Right, looks like it comes from the "good old times" when on Linux computers
software was "installed" by downloading, then doing a "make" and a "make
install" in order to get it running, while nowadays "ins
>Le lun. 7 oct. 2019 à 16:49, Cornelis Bockemühl a
>écrit :
>
>> Thanks to both you and J Decker: I would say that this is still the part
>> that I understood! So basically the word "install" in cmake language could
>> be replaced by "copy" more or
Thanks to both you and J Decker: I would say that this is still the part that I
understood! So basically the word "install" in cmake language could be replaced
by "copy" more or less in common human language - right?
But then, if it is about "installing" a "target", which is libraries in my
ca
ning in it...
So IF such a thing exists, like a comprehensive explanation about what
"install" actually means and what it is supposed to do at what stage of the
process, I would be very happy and thankful!
Best regards,
Cornelis
--
Powered by www.kitware.com
Please keep messages o
if the software could just as well tell
you exactly what the problem is...
Best regards,
Cornelis
Am Sonntag, September 22, 2019 21:46 CEST, Craig Scott
schrieb:
You may want to take a look at the BUILDSYSTEM_TARGETS directory property. It
might not be quite what you're looking for, but
quot;code deserts" with one line of code.
And because this is so fundamental in my eyes, I still almost assume that also
for targets and properties there must be some function available - which I
simply have not found yet!??
Or else I would consider this an urgent feature request!
Best regar
er "feature requests"?
In fact I can hardly believe that I am the first with such kind of dreams, so
my hope is still that they already exist somewhere...
--
Cornelis Bockemühl
mail: corne...@bockemuehl.ch
phone: +41 79 644 9943
Basel, Switzerland
https://cobo.bockemuehl.ch
--
Powe
option to change it.
My guess is that I would need an additional "flag" variable that tells
the sub project whether it is now being built within the main project
or standalone. Again not so nice, but besides the "brute force
solution" (hardcoded) the only one that I can see to
ch a code, so ... what are the experts doing in such a case?
Thanks and regards,
Cornelis--
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 support the CMake community. For more
inform
se I
have CMake!
Regards,
Cornelis
Am Samstag, den 31.03.2018, 08:19 + schrieb Tarmo Pikaro via CMake:
> Hi !
>
>
> > On my own free time I've managed to create tool similar to cmake -
command line tool called syncProj.
>
>
> > > Currently syncProj is
ase during development I decided to
stay with the QtCreator - CMake - ninja "team of tools"!
Regards, Cornelis
Am Samstag, den 17.02.2018, 08:06 +0100 schrieb Cornelis Bockemühl:
> Thanks also for this hint: I will give it a try!
>
> Regards, Cornelis
>
> Am Freitag,
Thanks also for this hint: I will give it a try!
Regards, Cornelis
Am Freitag, den 16.02.2018, 21:35 +0300 schrieb Konstantin Tokarev:
>
> > 16.02.2018, 21:32, "Cornelis Bockemühl" :
> > Thanks - that did the trick!
> >
> > > > > > And indeed b
ule by module, or whatever.
Anyway, my question is answered - thanks again!
Regards,
Cornelis
Am Freitag, den 16.02.2018, 20:25 +0300 schrieb Konstantin Tokarev:
>
>
> > 16.02.2018, 20:20, "Cornelis Bockemühl" :
> > > > Thanks for your hints! And you are righ
target SecondModule
...
===
For example I do not really understand all the parameters that are
passed to cmake - and I do not find them in the documentation either
(like -H, -B or --check-build-system...
Regards,
Cornelis
Am Freitag, den 16.02.2018, 08
ress for it, so I get an error message.
Basically I think that it is 99% a CMake question and maximum 1% a
QtCreator problem, so I am asking this question here.
And now I am stuck - if not some friendly and knowing person can help
me out of this!
Thanks for any helpful hint!
Cornelis--
Powered b
What a shame! Actually that error message comes from my own
CMakeLists.txt file - where I had so far only configured some settings
for Linux and not yet for MSVC...
This is indeed not any more the MT problem, but simply my own - so
please forget about my previous posting!
Regards, Cornelis
Am
probably simply downgrade to the previous version 3.9, but still I
wanted to report this problem to the experts!
Regards, Cornelis--
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 support the
Thanks - that was it! Now CMake is happy - just a question of
seconds...
Regarcs, Cornelis
Am Donnerstag, den 09.11.2017, 09:30 + schrieb CHEVRIER, Marc:
>
>
> > The problem is on NAMES argument. You have to specify library names
without prefix. So
> Clp must be used rat
})
MESSAGE(AUTHOR_WARNING ${COINUTILS_LIBRARY})
MESSAGE(AUTHOR_WARNING ${OSI_LIBRARY})
MESSAGE(AUTHOR_WARNING ${OSICLP_LIBRARY})
A dir for the indicated directory shows the following files:
-rwxrwxrwx 1 cornelis users 907 8. Nov 18:37 libClp.la
lrwxrwxrwx 1 cornelis users 42 8. Nov 18:37
25 matches
Mail list logo