[PD-cvs] externals/grill/flext build.txt, 1.5, 1.6 package.txt, 1.9, 1.10 - Pd-cvs

19 Apr 2005


      Update of /cvsroot/pure-data/externals/grill/flext
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23509
Modified Files:
    build.txt package.txt 
Log Message:
fixed typo
added profiling flags for OSX
small fixes
Index: package.txt
===================================================================
RCS file: /cvsroot/pure-data/externals/grill/flext/package.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** package.txt	13 Apr 2005 00:24:17 -0000	1.9
--- package.txt	19 Apr 2005 13:29:51 -0000	1.10
***************
*** 32,36 ****
    flutil.cpp flatom.cpp flatom_pr.cpp flthr.cpp fltimer.cpp flsimd.cpp flout.cpp \
    flatom_part.cpp flitem.cpp flmeth.cpp flmsg.cpp \
! 	flproxy.cpp flqueue.cpp flbind.cpp
  HDRS= \
    flprefix.h flstdc.h flbase.h flclass.h flext.h flsupport.h flmap.h fldsp.h flinternal.h flcontainers.h \
--- 32,36 ----
    flutil.cpp flatom.cpp flatom_pr.cpp flthr.cpp fltimer.cpp flsimd.cpp flout.cpp \
    flatom_part.cpp flitem.cpp flmeth.cpp flmsg.cpp \
! 	flproxy.cpp flqueue.cpp flbind.cpp flmap.cpp
  HDRS= \
    flprefix.h flstdc.h flbase.h flclass.h flext.h flsupport.h flmap.h fldsp.h flinternal.h flcontainers.h \
Index: build.txt
===================================================================
RCS file: /cvsroot/pure-data/externals/grill/flext/build.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** build.txt	25 Mar 2005 04:52:21 -0000	1.5
--- build.txt	19 Apr 2005 13:29:51 -0000	1.6
***************
*** 67,71 ****
  Please note, that the build system is shell-oriented, which means, that you'll have
  to launch a command prompt (cmd.exe under Windows) and probably also set some
! environment variables for your development system (e.g. run vcvars32.bat for Microsoft Visual Studio)
By invoking one of the build scripts (e.g. with "bash build.sh" under unix, 
--- 67,71 ----
  Please note, that the build system is shell-oriented, which means, that you'll have
  to launch a command prompt (cmd.exe under Windows) and probably also set some
! environment variables for your development system (e.g. run vcvars32.bat included with Microsoft Visual Studio)
By invoking one of the build scripts (e.g. with "bash build.sh" under unix,