> Why would you copy functionality that the OS provides out of the box ?
I profit that you are here Michael !
Not everybody knows perfectly his os.
Dealing with dynamically libraries helps to not oblige end-users to copy
files into root-protected-directories.
But, like explained, if that dynamically loaded library depends on other
libraries you have to define the library-search path for that dependencies.
And here we come.
With fpc, that knows lot of os (unlike other compilers), with use of:
{$ifdef linux}{$define something}{$endif}
{$ifdef freebsd}{$define somethingelse}{$endif}
{$ifdef windows}{$define somethingdifferent}{$endif}
...
you may help a lot end-users (and developers)
Take a look at stackoverflow or other developer forum: "how to define path
of libraries" is asked looot of times.
> (2) Why would you copy functionality that the OS provides out of the box ?
Ha, then you know the command to use... ;-)
This command will be added in the TProcess used by TLoadLibrary.LibraryPath.
And this, with help of all the fpc-gurus, for each OS.
Fre;D
-----
Many thanks ;-)
--
View this message in context:
http://free-pascal-general.1045716.n5.nabble.com/uses-myunit-in-src-myunit-pas-tp5727626p5727648.html
Sent from the Free Pascal - General mailing list archive at Nabble.com.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
