Re: SharedLIbrary with SHLIBVERSION

Thanks for the info... The short answer is package generation in Parts. I was not seeing symlinks as it was expected to be in the emit list of the builder, like it is for windows as an example which emit the pdb, export lib, etc. The rpm packages I was generating had missing symlinks when the SHLIBVERSION was used. The symlinks when I defined them in Parts as FileSymbolicLink node showed up correctly. It should be a simple fix on my end.

Jason
________________________________
From: Scons-users <[email protected]> on behalf of Bill Deegan <[email protected]>
Sent: Tuesday, April 23, 2019 9:56 AM
To: SCons users mailing list
Subject: Re: [Scons-users] SharedLIbrary with SHLIBVERSION

If you use Install, it should also install the symlinks.
What's your use case here that needs this information?

On Fri, Apr 19, 2019 at 5:03 PM Jason Kenny <[email protected]<mailto:[email protected]>> wrote:
Just a quick question.

shouldn't SharedLIbrary() return the symlinks that it will generate? they are targets it generates however it does not return nodes to these items in the list

example:

out  = env.SharedLibrary(target='mylib',source="a.c", SHLIBVERSION='1.2.3')
print([str(i) for i in out])

results in the
['libmylib.so.1.2.3']

I would have expected:
['libmylib.so.1.2.3','libmylib.so.1.2','libmylib.so.1','libmylib.so']


Jason
_______________________________________________
Scons-users mailing list
[email protected]<mailto:[email protected]>
https://pairlist4.pair.net/mailman/listinfo/scons-users<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpairlist4.pair.net%2Fmailman%2Flistinfo%2Fscons-users&data=02%7C01%7C%7C4f41a83cc91f4c3b20e908d6c7fbe539%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636916282022382696&sdata=QZkPojmnRbu65DToqTi4gyD%2BMeqOuI8PlUGamBOH%2Fas%3D&reserved=0>

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users