projects / wxWidgets.git / blame
| Commit | Line | Data |
|---|---|---|
| 4e937c4d RD |
1 | # This file gives the details of what is needed to build this extension |
| 2 | # module so the Makefile can be created. | |
| 3 | ||
| 4 | ### | |
| 5 | ### This file should be created by configure. Currently it is tweaked by hand. | |
| 6 | ### | |
| 7 | ||
| 8 | *shared* | |
| 9 | ||
| 10 | CCC=c++ | |
| 11 | WXWIN=../../.. | |
| 12 | GENCODEDIR=gtk | |
| 13 | srcdir=$(GENCODEDIR) | |
| 14 | ||
| 15 | # Depending on how your Python was built, you may have to set this | |
| 16 | # value to use the C++ driver to link with instead of the default | |
| 17 | # C driver. For example: | |
| 18 | MY_LDSHARED=$(CCC) -shared | |
| 19 | ||
| 20 | # Same as above, but for statically linking Python and wxPython together, | |
| 21 | # in other words, if you comment out the *shared* above. If this is the | |
| 22 | # case then you should ensure that the main() function is Python's, not | |
| 23 | # wxWindows'. You can rebuild $(WXWIN)/src/gtk/app.cpp with NOMAIN defined | |
| 24 | # to force this... | |
| 25 | MY_LINKCC=$(CCC) | |
| 26 | ||
| 27 | ||
| 28 | ## Pick one of these, or set your own. This is where the | |
| 29 | ## wxPython module should be installed. It should be a | |
| 30 | ## subdirectory named wxPython. | |
| 31 | TARGETDIR=.. | |
| 32 | #TARGETDIR=$(BINLIBDEST)/site-packages/wxPython | |
| 33 | ||
| 34 | ||
| 35 | wxpc wxp.cpp helpers.cpp windows.cpp events.cpp misc.cpp gdi.cpp \ | |
| 36 | mdi.cpp controls.cpp controls2.cpp windows2.cpp cmndlgs.cpp \ | |
| 37 | frames.cpp stattool.cpp \ | |
| 38 | # CFLAGS | |
| 39 | -I. -I$(WXWIN)/include -I/usr/lib/glib/include -I$(WXWIN)/src \ | |
| 40 | -I/usr/X11R6/include -DSWIG_GLOBAL -D__WXGTK__ \ | |
| 41 | #-D__WXDEBUG__ \ | |
| 42 | # LFLAGS | |
| 43 | -L$(WXWIN)/lib/Linux -L/usr/X11R6/lib \ | |
| 44 | -lwx_gtk -lgtk -lgdk -lglib -lXext -lX11 |