Okay so just to document it, above approach has a flaw, and that was the reason I originally mentioned the need to rearrange dirs. The flaw is that it will fail to create harbour dynlib when doing a partial build inside /source, unless we've previously done a build of hbpcre / hbzlib in one way or another, in a separate pass. Probably we can live with it, but it may be important to note anyway.You are right that it will not work but we have similar problem also before because it was not possible to create harbour.dll without recompiling harbour external/{hbpcre,hbzlib} which were needed to create final binaries. Now the same is true also on platforms which allows to create shared libraries with unresolved references (late binding). If we begin to use zlib in more places, i.e. for generating compressed .hrb or .hrl files by compiler then it will not be possible to even start any compilation without compiling external/hbzlib if system ZLIB library does not exists. Anyhow I do not find it as critical. Even now you cannot start compilation in any directory containing .prg files if harbour compiler was not compiled before.
Yes, that's right, I agree it's safe to settle on this compromise. I was about to correct one of my (unrelated to this) replies, so I stick it here: on darwin the multiple compiler tool in PATH issue is not present, since clang isn't put there by default. I'll have to correct detection logic to look into its default location. Brgds, Viktor _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
