[fpc-pascal] Fatal: Can't find unit GL used by GLPT
___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Fatal: Can't find unit GL used by GLPT
Hi, I'm trying to setup Travis CI for GLPT. The build script is: wget -q ftp://ftp.freepascal.org/pub/fpc/snapshot/v33/i386-win32/fpc-3.3.1.i386-win32.zip ; mkdir fpc; unzip -q -d fpc fpc-3.3.1.i386-win32.zip; export PATH="$PATH":"$PWD/fpc/bin/i386-win32/"; For a simple hello world app it works perfectly. For GLPT, FPC cannot find the GL unit. Is this an fpc.cfg issue? How to solve this problem? The project including Travis CI script is located here: https://github.com/daar/GLPT TIA! Darius On Fri, Apr 5, 2019 at 9:59 AM Darius Blaszyk wrote: > > ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
[fpc-pascal] Public key algo pascal only
Hello, Is there any public/private key algorithm, pascal only, implemented in the distribution of fpc ? Degree of security is not important, also a 3rd party unit which does not depends on a DLL or depends on another software to generate key pairs, or other tasks, would be valid too. Thank you. -- ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Public key algo pascal only
On Fri, 5 Apr 2019, José Mejuto wrote: Hello, Is there any public/private key algorithm, pascal only, implemented in the distribution of fpc ? Degree of security is not important, also a 3rd party unit which does not depends on a DLL or depends on another software to generate key pairs, or other tasks, would be valid too. Not to my knowledge. All solutions use gnutls or openssl. I know of TMS Crypto, but it also uses .obj files that were generated using C, as far as I know. Maybe DCrypt has the necessary routines, Graeme Geldenhuys maintains a version that works with FPC. Michael.___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Public key algo pascal only
El 05/04/2019 a las 13:01, Michael Van Canneyt escribió: Maybe DCrypt has the necessary routines, Graeme Geldenhuys maintains a version that works with FPC. Hello, Thank you, I have code from DCrypt but I was looking for something much more simple which can generate the keys/certificates and handle all operations or at least sign/check-sign, even a 32 bits algo would be valid :-) Anyway thank you, your answer confirms my suspects. -- ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Compile for WinCE 7, target ARM, CPU Cortex-A9
Drawback is that I must now maintain 2 FPC installations/cross-compilers (Win32-WinCE): one for targer WinCE 5,6 with CPUs ARMv5 and another for WinCE 7 with ARMv7 CPU (It is not sufficient to setup build modes in project ... also all units must be pre-compiled ... at least I do not know how to bypass this limitation) I suspect your problem is related to this feature request: https://bugs.freepascal.org/view.php?id=30294 Yes seems so ... Note that you probably don't need two different cross compilers if your cpu-OS target is the same Target CPU family is same: "arm", but Target processor is not the same: "ARMv4" versus "ARMv7" ... So I do not know if this requires two pre-compiled cross-compilers or not? , only two different versions of the RTL (and perhaps packages) in a way that enables the compiler to pick the correct version. For avr-embedded I change the unit output folder name to avr-embedded-SUBARCH and add the subarch macro to fpc.cfg. For arm you may also need to handle different ABI versions (I don't cross compile for arm). I can set in Project Options "Unit Output Directory", but how to set where RTL/packages are located ... Perphas recompilation RTL/packages for given target processor from sources is okay for me, but is it doable in one Lazarus with one cross compiler? -Laco. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Compile for WinCE 7, target ARM, CPU Cortex-A9
LacaK schrieb am Fr., 5. Apr. 2019, 13:18: > > > Note that you probably don't need two different cross compilers if your > cpu-OS target is the same > > Target CPU family is same: "arm", but Target processor is not the same: > "ARMv4" versus "ARMv7" ... > > So I do not know if this requires two pre-compiled cross-compilers or not? > You only need different compilers if you have different ABIs (e.g. Soft Float vs. Hard Float). For WinCE that isn't applicable however. Regards, Sven > ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Compile for WinCE 7, target ARM, CPU Cortex-A9
Note that you probably don't need two different cross compilers if your cpu-OS target is the same Target CPU family is same: "arm", but Target processor is not the same: "ARMv4" versus "ARMv7" ... So I do not know if this requires two pre-compiled cross-compilers or not? You only need different compilers if you have different ABIs (e.g. Soft Float vs. Hard Float). For WinCE that isn't applicable however. So it does not matter how I build cross-compiler using FpcUpDeluxe: wheter I use "-Cparmv5" or "-Cparmv7A" ? Then there is still problem with precompiled RTL/packages? Because when I only change "Target processor" (in Lazarus build using FpcUpDeluxe) I can compile application, but I can not run it on target system (so I guess, that resulting EXE is not compiled for target processor). When I add to Custom options: -CfVFPV2 then I get error while compiling: Fatal: Can't find unit system used by Test1 When I download and install default Lazarus and cross-compiler then when I change "Target processor" to "ARMv5" or "ARMv7A" I get: "project1.lpr(22,0) Error: Error while assembling exitcode 1" -Laco. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Compile for WinCE 7, target ARM, CPU Cortex-A9
LacaK schrieb am Fr., 5. Apr. 2019, 14:56: > > >> >> Note that you probably don't need two different cross compilers if your >> cpu-OS target is the same >> >> Target CPU family is same: "arm", but Target processor is not the same: >> "ARMv4" versus "ARMv7" ... >> >> So I do not know if this requires two pre-compiled cross-compilers or not? >> > You only need different compilers if you have different ABIs (e.g. Soft > Float vs. Hard Float). For WinCE that isn't applicable however. > > So it does not matter how I build cross-compiler using FpcUpDeluxe: wheter > I use "-Cparmv5" or "-Cparmv7A" ? > Correct. Then there is still problem with precompiled RTL/packages? > > Because when I only change "Target processor" (in Lazarus build using > FpcUpDeluxe) I can compile application, but I can not run it on target > system (so I guess, that resulting EXE is not compiled for target > processor). > > When I add to Custom options: -CfVFPV2 then I get error while compiling: > Fatal: Can't find unit system used by Test1 > > When I download and install default Lazarus and cross-compiler then when I > change "Target processor" to "ARMv5" or "ARMv7A" I get: "project1.lpr(22,0) > Error: Error while assembling exitcode 1" > As said by Christo you need to select the correct set of compiled units. Also you need to select the correct processor type when building your application. Regards, Sven ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Public key algo pascal only
Hi, try this https://github.com/delphi-pascal-archive/Pascal-RSA пт, 5 апр. 2019 г. в 14:17, José Mejuto : > El 05/04/2019 a las 13:01, Michael Van Canneyt escribió: > > > Maybe DCrypt has the necessary routines, Graeme Geldenhuys maintains a > > version that works with FPC. > > Hello, > > Thank you, I have code from DCrypt but I was looking for something much > more simple which can generate the keys/certificates and handle all > operations or at least sign/check-sign, even a 32 bits algo would be > valid :-) > > Anyway thank you, your answer confirms my suspects. > > -- > > ___ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal -- Victor Matuzenko (Виктор Матузенко) ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
