Changeset 1921
- Timestamp:
- 04/07/08 04:06:42 (9 months ago)
- Location:
- branches/c08_branch/source
- Files:
-
- 4 modified
Legend:
- Unmodified
- Added
- Removed
-
branches/c08_branch/source/cpu.cpp
r1824 r1921 208 208 209 209 /* if the environment variable was not set, the default set in path.h takes effect */ 210 string chSearchPathRaw = ( path != NULL ) ? string( path ) : string( LOCAL_DATA_PATH );210 string chSearchPathRaw = ( path != NULL ) ? string( path ) : string( CLOUDY_DATA_PATH ); 211 211 212 212 # ifdef _WIN32 … … 490 490 fprintf( ioQQQ, "the most likely reason is that the path has not been properly set.\n"); 491 491 fprintf( ioQQQ, "Please have a look at the file path.h in the source directory.\n"); 492 fprintf( ioQQQ, "Check how the variable LOCAL_DATA_PATH is set - ");492 fprintf( ioQQQ, "Check how the variable CLOUDY_DATA_PATH is set - "); 493 493 fprintf( ioQQQ, "it should give the location of the data files I need.\n"); 494 494 fprintf( ioQQQ, "These are the files in the data download from the web site.\n"); -
branches/c08_branch/source/Makefile
r1900 r1921 113 113 114 114 cpu.o: 115 ${CXX} ${CXXFLAGS} -c -D LOCAL_DATA_PATH=\"${CDP}\" $<115 ${CXX} ${CXXFLAGS} -c -DCLOUDY_DATA_PATH=\"${CDP}\" $< 116 116 117 117 # an explicit -O0 is needed for some compilers like icc -
branches/c08_branch/source/path.h
r1817 r1921 11 11 * The location of these data on your system is specified by 12 12 * 13 * #define LOCAL_DATA_PATH "XXXX"13 * #define CLOUDY_DATA_PATH "XXXX" 14 14 * 15 15 * below, so the code is set up so that data will be automatically … … 22 22 * The data path can also be set by the CLOUDY_DATA_PATH environment 23 23 * variable, but it is generally easier to provide the permanent 24 * location at compile time by editing LOCAL_DATA_PATH below.24 * location at compile time by editing CLOUDY_DATA_PATH below. 25 25 */ 26 26 27 27 /* The value below will be superseded if 28 28 * specified by a compiler argument */ 29 #ifndef LOCAL_DATA_PATH29 #ifndef CLOUDY_DATA_PATH 30 30 31 31 /* … … 36 36 * can enter as many paths as you like. One example could be: */ 37 37 38 #define LOCAL_DATA_PATH "/usr/local/cloudy/data:/home/user/cloudy/data"38 #define CLOUDY_DATA_PATH "/usr/local/cloudy/data:/home/user/cloudy/data" 39 39 40 40 … … 44 44 * NB - note that the backslash "\" always needs to be typed twice, as shown below: */ 45 45 46 // #define LOCAL_DATA_PATH "c:\\projects\\cloudy\\data;c:\\users\\gary\\data"46 // #define CLOUDY_DATA_PATH "c:\\projects\\cloudy\\data;c:\\users\\gary\\data" 47 47 48 48 /* The // makes the above line of code a comment -
branches/c08_branch/source/vs.txt
r1799 r1921 3 3 set path 4 4 project / trunk properties / c/c++ / preprocessor / preprocessor definiation - at after ; 5 LOCAL_DATA_PATH="\"c:\\projects\\cloudy\\trunk\\data\\\\\""5 CLOUDY_DATA_PATH="\"c:\\projects\\cloudy\\trunk\\data\\\\\"" 6 6 7 7 inline functions - use even in debug - factor of 2 speedup: … … 27 27 in an error and a failed compile. You can also manage this from your code by 28 28 including a header file listing all the rules and their default state. You 29 can then upgrade warnings to errors or disable warnings using the #pragma directive. 29 can then upgrade warnings to errors or disable warnings using the #pragma 30 directive. 30 31 31 32 ================================ … … 42 43 and how it was called. Instrumentation involves inserting new code that 43 44 reports back the state of the application as it executes. As such it is much 44 more intrusive, but instrumentation profiling does illicit more information than sampling. 45 more intrusive, but instrumentation profiling does illicit more information 46 than sampling. 45 47 46 48 Application performance has become a major issue today. To help developers get an
