Why my modification on .scm cannot works?

[Christian Stimming]

Am Friday 07 May 2010 schrieb Tao Wang:
> I found it's actually loading the file
> "C:\soft\gnucash\inst\share\gnucash\guile-modules\gnucash\report\stylesheet
> -css.scm", which is the location of building package. It doesn't make any
> sense. I didn't find any enviroment variable point to the building
> location.

I'm afraid this means the gnucash windows binary still contains a compiled-in 
path location of the installation patch during compiling which is searched 
*first*.

Try renaming your c:\soft\gnucash\inst folder into inst-disabled. You should 
recognize the program now loads from your "real" installation location because 
this original compiled-in path does no longer exist.

Nevertheless we should change the search order so that the real installation 
location has precedence over any path that was compiled-in at compile time. 
Sorry for that. Having all paths compiled-in at compile time is the "old 
school Unix style" and we're having a hard time to get away from it.

Regards,

Christian

> 
> On Fri, May 7, 2010 at 4:19 PM, Tao Wang <dancefire at gmail.com> wrote:
> > Hi,
> > 
> > I found something strange. I'm using the win32 package I build myself,
> > it's the lastest one. After installation, I found a bug in "C:\Program
> > Files\gnucash\share\gnucash\guile-modules\gnucash\report\stylesheet-css.s
> > cm", so I modified it. And then I reboot the GnuCash, and the report
> > result is still as same as before. Then, I reboot my computer, the
> > result is still same. And, I rename the file "stylesheet-css.scm",
> > reboot the GnuCash, GnuCash is still working, and the report in "Default
> > CSS" is still as same as before.
> > 
> > Why my modification doesn't work? Is the .scm compiled during the
> > building package?
> > 
> > --
> > Regards
> > 
> > Tao Wang