fivedev/harbour-core
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

2012-04-12 12:35 UTC+0200 Viktor Szakats (harbour syenar.net)

Browse Source 
* INSTALL
    + extended TROUBLESHOOTING about generic common-sense 
      information about not overdoing custom configuration, 
      especially for C compiler. I didn't specifically include 
      anything about bcc, but let me here note, that hbmk2 
      and Harbour core build system doesn't require bcc32.cfg 
      and ilink32.cfg to be _present at all_ since quite long, 
      so please remove them for best results.
This commit is contained in:
Viktor Szakats
2012-04-12 10:38:03 +00:00
parent 5906641479
commit 749f7db2c9
2 changed files with 25 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
harbour/ChangeLog
View File

@@ -16,6 +16,16 @@
The license applies to all entries newer than 2009-04-28.
*/
2012-04-12 12:35 UTC+0200 Viktor Szakats (harbour syenar.net)
* INSTALL
+ extended TROUBLESHOOTING about generic common-sense
information about not overdoing custom configuration,
especially for C compiler. I didn't specifically include
anything about bcc, but let me here note, that hbmk2
and Harbour core build system doesn't require bcc32.cfg
and ilink32.cfg to be _present at all_ since quite long,
so please remove them for best results.
2012-04-12 00:13 UTC+0200 Viktor Szakats (harbour syenar.net)
* src/rtl/fscopy.c
* reverted last change targeting hb_fs* -> hb_file* conversion.

18
harbour/INSTALL
View File

@@ -1265,7 +1265,9 @@ HARBOUR
set PATH=C:\<compilerdir>
If you use Harbour official binary distro on Windows, even above is
unnecessary and not recommended.
6. Remove all old, unnecessary environment variables from your environment.
6. Remove all old, unnecessary environment variables (for both Harbour
and C compiler) from your environment. Also remove any custom settings
for your C compiler.
Use only those documented in this file.
Follows some environment variable settings which are commonly believed
by users to be useful, but which in reality are either not needed or
@@ -1303,8 +1305,18 @@ HARBOUR
10. Do not alter the directory layout and files in Harbour and 3rd party
packages.
11. If you are to report a build problem with a Harbour application,
most of the above point applies, plus make sure to use '-trace'
command line option when running hbmk2.
most of the above points apply, plus make sure to use '-trace'
command line option when running hbmk2 and redirect the result to
a file (see above how).
It's a good idea to first remove all manual references to Harbour
core components from make files and custom environment. F.e. it's
commom mistake to add C compiler header and/or lib dirs, Harbour core
header and/or lib dirs, built-in constants to make files or environment.
No such thing is necessary and all of these is automatically handled
by hbmk2. IOW start simple and don't be overbusy with "fine-tuning"
your configuration, if you need to, the problem is most probably
elsewhere. It's also good idea to try with Harbour nightly binary or
official release first.
12. If you are to report a problem with Harbour itself, always provide
self-contained, minimal source code example. Do not use xhb contrib
library, or any 3rd party Harbour libraries. The example shall reproduce