Boost logo

Boost :

From: Ruben Perez (rubenperez038_at_[hidden])
Date: 2024-12-22 16:46:05


On Sun, 22 Dec 2024 at 17:27, Peter Dimov <pdimov_at_[hidden]> wrote:
>
> Ruben Perez wrote:
> > On Sun, 22 Dec 2024 at 17:02, Peter Dimov via Boost <boost_at_[hidden]>
> > wrote:
> > >
> > > Ruben Perez wrote:
> > > > install(TARGETS ${LIB} EXPORT ${LIB}-targets
> > > > RUNTIME DESTINATION "${CMAKE_INSTALL_BINDIR}"
> > > > LIBRARY DESTINATION "${CMAKE_INSTALL_LIBDIR}"
> > > > ARCHIVE DESTINATION "${CMAKE_INSTALL_LIBDIR}"
> > > > PRIVATE_HEADER DESTINATION "${CMAKE_INSTALL_INCLUDEDIR}"
> > > > PUBLIC_HEADER DESTINATION "${CMAKE_INSTALL_INCLUDEDIR}"
> > > > FILE_SET CXX_MODULES DESTINATION .
> > > > )
> > >
> > > `DESTINATION .`? Where does this put the module files? In /usr?
> >
> > No. It places them under ${CMAKE_INSTALL_PREFIX}/./modules/${LIB}.cxx.
>
> If we assume the default prefix of /usr, this means /usr/modules/core.cxx,
> which doesn't seem quite right on a number of levels.
>
> My instinct was to call the source file boost_core.cppm, and it seems like
> it was correct.
>
> The current convention for modules seems to be either
> CMAKE_INSTALL_LIBDIR or CMAKE_INSTALL_DATADIR.
>
>

True. Will change it.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk