On 8/2/2013 1:53 PM, Nat Echols wrote: > I am attempting to modify the C++ code for an application (coot) which > effectively requires the use of Fink to build on OS X. At the suggestion > of the package maintainer, I tried starting with this command: > > sudo fink -k -K rebuild coot > > which leaves the source directory in place. However, any attempt to run > "make" in that directory after modifying the code fails, despite having the > Fink environment variables set. I tried searching for additional > information, and found some additional suggested environment variables, but > those don't help either. Re-running the fink command above simply wipes > out the directory and replaces it with a clean copy; I couldn't find any > solution for that other than modifying the Perl code for Fink. > > So, I think I need to start over: what is the recommended mechanism for > rebuilding from source? Is there a standard way to set up the environment > to be identical to what Fink uses internally when building packages? > > (PS. OS 10.7, latest Xcode and command-line tools.)
http://finkers.wordpress.com/2009/07/24/creating-local-packages/ has instructions on how to generate a local copy of the instructions Fink uses to build a package. You can then modify the copied coot.info and coot.patch files with whatever changes you might want. If you're still testing out changes and want to do a quick test on Fink expanded source tree left over after using the -k flag, cd into the build directory (/sw/src/fink.build/coot-0.7.1.0-3/coot-0.7.1, then "chown -R <YOURID>:admin . " so that you have write permissions, patch the code, set the flags as needed (don't forget to *prepend* /sw/var/lib/fink/path-prefix-clang to $PATH), and try make again. If something is still failing, please post the error (or the unexpected result) you're getting from that command rather than just saying 'it fails'. It's not identical (especially for non-C based programs) to the internal Fink environment, but when I need to test local changes, I set the following variables during my tests: export FINK_PREFIX=/sw export PATH=${FINK_PREFIX}/var/lib/fink/path-prefix-clang:$PATH export CPPFLAGS=-I${FINK_PREFIX}/include export LDFLAGS=-L${FINK_PREFIX}/lib Hanspeter ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
