[Scons-users] ParseDepends and duplicate with variant directories
Bill Deegan
bill at baddogconsulting.com
Mon Dec 18 14:49:01 EST 2017
Any such patch would have to work with all currently supported compilers to
replace the existing scanner.
(Or be enablable on a compiler by compiler basis)
Also it's performance would have to be comparable to the current C/C++
scanner.
Then there would be a period of community review.
I'd suggest if you want to go down that path to get what you have
functional (with tests) and push to scons-contrib so others can try it out.
On Mon, Dec 18, 2017 at 12:46 PM, Gaurav Juvekar <gauravjuvekar at gmail.com>
wrote:
> Hi,
>
> > You might consider picking up the pull request still on bitbucket for a
> > more complete C scanner implementation which does much of the
> preprocessor
> > logic.
>
> Instead of improving the C scanner implementation, would a patch be
> accepted for a scanner that actually invokes the compiler with all the
> flags and then uses ParseDepends? It just seems "more correct" to use the
> compiler generated dependencies instead of parsing the file using a scanner
> like it's currently done. This way, the compiler can handle any crazy
> include combinations (even those that rely on compiler builtins such as
> #include_next). I know that this could be way slower than using a parser in
> Python.
>
> >
> > What's driving you to use the compiler itself to generate the
> dependencies?
> >
>
> Crazy organization in a third-party project whose source I can't change.
>
> --
> Regards,
> Gaurav Juvekar
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20171218/739b4eb3/attachment.html>
More information about the Scons-users
mailing list