Mac OS X developpement build
Hi list,
Thanks to the help of Michael Wybrow who made the process really easy I have a development binary of inkscape for mac os X build from last CVS snapshot. Here is what is activated at the end of the compilation process. Is it OK or do you want gnome-print and gnome-vfs?
Configuration:
Source code location: . Destination path prefix: /Volumes/files/softwares/inkscape_compiled/ Compiler: g++ CPPFLAGS: -I/sw/include -O3 -Wall CXXFLAGS: -Wall -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -I/sw/include -O3 -Wall CFLAGS: -Wall -W -I/sw/include -O3 -Wall LDFLAGS: -L/sw/lib
Use Xft font database: yes Use gnome-print: no Use gnome-vfs: no Use openoffice files: yes Use MMX optimizations: no Use relocation support: no Use Python extensions: skipped Use Perl extensions: skipped Enable Inkboard: no
If this is ok, where should I put it now? I have no space to host it myself. If this proves to be useful I plan on making such a build on a weekly basis.
JiHO --- Windows, c'est un peu comme le beaujolais nouveau : a chaque nouvelle cuvee on sait que ce sera degueulasse, mais on en prend quand meme par masochisme. --- http://jo.irisson.free.fr/
On Thu, Sep 15, 2005 at 01:07:45PM +0200, jiho wrote:
Here is what is activated at the end of the compilation process. Is it OK or do you want gnome-print and gnome-vfs?
gnome-print should stay off. gnome-vfs is a "nice to have", and lets you load URLs from the commandline.
If this is ok, where should I put it now? I have no space to host it myself. If this proves to be useful I plan on making such a build on a weekly basis.
We can make another directory up on sourceforge, alongside the win32 snapshots.
participants (2)
-
jiho
-
Kees Cook