Hi,
and thanks for your quick reply!
Starting from a minimal, stripped down version of my build
configuration (thx for the tip!) I found that what I described
initially actually works. The reason it was not working was, that I
had turned the CPACK_SET_DESTDIR flag on in another place. After
remov
2015-06-19 21:13 GMT+02:00 Rainer Poisel :
> Dear list,
>
> how can I specify different installation prefixes for the different
> CPACK_GENERATORs?
>
> For example:
>
> * the DEB package should be installed to `/opt/project`
> * the TGZ archive should consist only of the `project` directory
>
Dear list,
how can I specify different installation prefixes for the different
CPACK_GENERATORs?
For example:
* the DEB package should be installed to `/opt/project`
* the TGZ archive should consist only of the `project` directory
>From the documentation I understood that I would have to us
2015-06-19 19:17 GMT+02:00 Tom Kacvinsky :
> I have need to build two libraries, each based on the same base code, but
> each library is built with different compiler options. I know how to force
> the compilation options to be what I want, the problem I am having is
> envisioning how to do this
I have need to build two libraries, each based on the same base code, but
each library is built with different compiler options. I know how to force
the compilation options to be what I want, the problem I am having is
envisioning how to do this within one CMakeLists.txt file. What I am hung
up o
Hello,
I discovered by accident that cmake (3.2.2) apparently respects the --prefix
command line option, with a result that's somewhat different from setting
CMAKE_INSTALL_PREFIX. I cannot seem to find any documentation on this feature
though: have I overlooked it, or is this indeed an undocume
> Great! Thanks for testing this.
No problem - thank YOU for supporting this compiler!
> It will be in the 3.4 release, which should come in the Fall.
Great -will keep an eye out for 3.4 release.
Thanks again,
Tony
This e-mail (including attachments) contains contents owned by Rolls-Royce plc
On 17 June 2015 at 22:58, Stephen Kelly wrote:
> Klaim - Joël Lamotte wrote:
>
> > Thinking about boost, if package files works well with header-only
> > libraries (which I
> > suppose it should as long as the boost define header-only targets)
> > then it would be very useful indeed.
>
> Yes, I w
I looked at it briefly one day, and I couldn't figure out a way to tie the
output of custom commands to the list of objects that add_library(OBJECTS)
produces.
Alternatively since all you want is a list of objects, FindCUDA can produce
this just as well.
Use the CUDA_WRAP_SRCS macro. It produces
