Re: [Visualpython-users] SConstruct

[Bruce S. <Bru...@nc...>]

I'm not an expert on makefiles, but I think the difference you see is
simply that the Linux makefile is explicit that .o files should be
built from .cpp files, whereas the Mac makefile takes advantage of the
default assumptions of makefiles, which I believe include the notion
that .o files should be built from .cpp files.

Bruce Sherwood

On Thu, Apr 19, 2012 at 10:34 AM, K.-Michael Aye <kmi...@gm...> wrote:
> On 2012-04-19 16:02:17 +0000, Bruce Sherwood said:
>
>> SConstruct was just an experience many years ago by Jonathan
>> Brandmeyer and is now irrelevant.
>
> Thanks, I am creating a cleaned up git branch ONLY for an Mac_EPD
> build. Thanks to git this can live totally independent from anything
> else, so I am kicking everything out that's not required anymore.
>
>>
>> There are three quite different build procedures, for Windows, Mac,
>> and Linux, each of them detailed in VCBuild/VCBuild.txt, MAC-OSX.txt,
>> and INSTALL.txt, respectively. And in the Linux case, in addition to
>> the complex autoconfigure machinery currently used to build the Linux
>> tarball posted at vpython.org, there is a simple makefile in src/gtk2
>> intended to give a sense of a basic build stripped to its essentials
>> and aimed specifically at Ubuntu.
>
> That was a good tip, thanks.
> That leaves me puzzled, how the makefile in src/mac actually can work?
> My makefile-foo is a bit rusty, but I am missing something like this
> line from the src/gtk2/makefile:
>
> %.o: %.cpp
>        $(CXX) $(CVISUAL_CPPFLAGS) $(CVISUAL_CXXFLAGS) -MMD -MF $*.d -MT "$*.d
> $*.lo" -c -o $@ $<
>
> in the src/mac version, that clearly makes use of the previously
> defined flags and tells the make system how to create all the objects.
>
> Still it seems the system gets the CXXFLAGS in the Mac's makefile
> somehow at build time, because when I comment them out, the errors I
> get look different.
> Just really puzzling…
>
> Michael
>
>
>>
>> Bruce Sherwood