Re: CMake linking errors [ctwmlib]

Yumekui Neru <[email protected]>
Newsgroups gmane.comp.window-managers.ctwm
Message-ID <VI1PR02MB1309038E923929215C4ACF09B0CE0@VI1PR02MB1309.eurprd02.prod.outlook.com>
On Wed, Oct 31, 2018 at 09:53:09PM -0500, Matthew D. Fuller wrote:
> A more likely and practical solution would be to try swapping around
> the order of the libs.  e.g.:
> 
> 
> === modified file 'CMakeLists.txt'
> --- CMakeLists.txt	2018-10-22 00:02:28 +0000
> +++ CMakeLists.txt	2018-11-01 02:51:09 +0000
> @@ -126,8 +126,8 @@
>  # with access to all our internal funcs.
>  add_library(ctwmlib STATIC ${CTWMSRC})
>  add_executable(ctwm "ctwm_wrap.c")
> +target_link_libraries(ctwm ctwmlib)
>  target_link_libraries(ctwm ${CTWMLIBS})
> -target_link_libraries(ctwm ctwmlib)
>  
>  # This doesn't really serve much purpose at the moment, so it's not even
>  # documented, but the code exists.  So make it buildable.
> 
> 
> so the .a is before the -l's, and see if that whips it into shape.
> 
> 
> -- 
> Matthew Fuller     (MF4839)   |  [email protected]
> Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
>            On the Internet, nobody can hear you scream.

This does make the build successful too.
My understanding from when I asked around for help with the issue was
that ctwm used to depend on ${CTWMLIBS} but it is now the new ctwmlib
that directly depends on them and that they should go there during
linking (hence the suggested replacement).
I do not know enough to say why one solution would be better/cleaner
or preferable over another though.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.