On Tue, 2012-01-10 at 08:08 +0100, res wrote: > On 10.01.2012 07:57, Philip Wyett wrote: > > Any other tips for new devs > > will be appreciated. Some of these we can always add to the CS docs as a > > cheat sheet. > > Once you started to actually modify source files you probably want to > exclude backup files as well; to accomplish that, pass ‘--exclude=*~’ on > the command line. >
Good tip. Another very dirty trick I use (and probably not the best way), is one to get preprocessor and assembly output of CS dumped out to file(s) for examination. After doing configure e.g. ./configure --enable-debug Go to your CS root directory and find/open 'Jamconfig' in your preferred editor. Now look for the lines: CMD.CC ?= gcc ; and CMD.C++ ?= g++ ; Now add 'save-temps' so your lines look like: CMD.CC ?= gcc -save-temps ; and CMD.C++ ?= g++ -save-temps ; Now save and build CS as you normally would. Note: This will create a lot of files and for those who want to look at a CS build at a low level. Not for the faint of heart. :-) Regards Phil ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ Crystal-main mailing list Crystal-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:crystal-main-requ...@lists.sourceforge.net?subject=unsubscribe
