Re: Setup.py questions
Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
| Newsgroups | gmane.comp.programming.tools.scons.devel |
|---|---|
| Message-ID | <CAEyG4CGiK1FgC0YQzAV7F_yJuFqHj_cJty=rdP0DCnf4tHexDQ@mail.gmail.com> |
Jason, 1 - See : https://bitbucket.org/scons/scons/commits/3ac389760cfe237ac449b4bbfa16ad7f03370dde basically building a win32 or win64 installer was failing if built on linux. (bdist_win32..) that's what this code fixes 2 - If we can simplify setup.py that would be great. I don't think we need any of the oddball install options which were put in place long before easy_install or pip or pypi for that matter. -Bill On Thu, Jun 2, 2016 at 10:41 AM, Jason Kenny <[email protected]> wrote: > > > Hi guys, > > > > I thought I would take a look at the setup.py file to see if I can clean > it up and make it better so we can pip install correctly. > > > > I was looking at the file and had a few questions: > > > > 1) Line 80 and 87 we have a reference to distutils.msvccompiler. > What is this for? We don’t need the compiler to install SCons > > 2) Is there a need to still install SCons in odd locations like > python/Scons? I think we are at a point in which simplifying this to allow > for scons to be installed in a standard location is good enough. Am I wrong? > > > > Thanks > > Jason > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev