per units, coderunner uses:
uses
{$IFDEF UNIX}
cthreads,
baseunix,
unix,
{$ENDIF}
{ huge list of units I developed }
variants,
keyboard,
PdfDocs,
PdfTypes,
PdfFonts,
SQLDb,
odbcconn,
sqlite3conn, <-- soon to remove, it's unstable in our testing
jansql, <-- soon to remove could not get it to work
spellcheck;
Those are the unit I run that I did not code.
Back to testing .sh idea.
PS. Worsecase, I can scrap 2.6.4 for 3.0.x - just been waiting for a stable
LLVM build for all 3 OSes I support.
On Wed, Jan 29, 2020 at 9:45 AM Marco van de Voort <
c...@pascalprogramming.org> wrote:
>
> Op 29/01/2020 om 16:07 schreef Ozz Nixon via fpc-devel:
>
> 1. My code does not directly interact with any environment variables.
>
> Unit cwstring and clocale might do on startup. This might influence e.g.
> widestring/unicodestring<-> ansistring conversions and back.
>
> 2. I am using version 2.6.4 to compile the daemon.
>
> That makes encoding debugging quite more difficult, as 2.6.4 behaves
> differently from 3.0.x in that regard.
>
>
>
> _______________________________________________
> fpc-devel maillist - fpc-devel@lists.freepascal.org
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
