Re: .def file generation issue with SCons

Bill Deegan <[email protected]>
Newsgroups gmane.comp.programming.tools.scons.user
Message-ID <CAEyG4CFnk4knmEQP-2Hia-N2MHKyTQRhh7Jxp6zbzrA2donxLg@mail.gmail.com>
Apparently cmake does this by using a helper executable to extract the
symbols from the object files.
It'd be doable, but IMHO general best practice is to use
__dllexport(symbol) and then for non-window platforms define that as a
macro which does nothing.
I've used that many times.

On Thu, Jul 15, 2021 at 11:12 AM Mats Wichmann <[email protected]> wrote:

> On 7/9/21 10:49 AM, Sumit Kothari wrote:
> > Hi,
> >
> > Just like WINDOWS_EXPORT_ALL_SYMBOLS generates .def file in CMake, if
> > you provide me steps to generate .def file using SCons in windows will
> > be of great help.
> > In SCons doc only the following lines are mentioned
> >
> > WINDOWS_INSERT_DEF
> >
> > When this is set to true, a library build of a Windows shared library
> > (.dll file) will also build a corresponding .def file at the same time,
> > if a .def file is not already listed as a build target. The default is 0
> > (do not build a .def file).
>
> just as an update, the docs in the next release will be updated not to
> make a claim the code doesn't back up.
>
>
> _______________________________________________
> Scons-users mailing list
> [email protected]
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users
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.