IIRC I used these: http://gnuwin32.sourceforge.net/packages/openssl.htm
Not sure about the file naming, but just put the .dll files in the same
directory as your executable. You'll know pretty quick if it works :)
On 04/18/2018 12:57 PM, Dennis wrote:
According to http://wiki.lazarus.freepasc
According to http://wiki.lazarus.freepascal.org/fphttpclient, I need the
openssl library if I want to use fphttpclient for https://www.yahoo.com/
From the wiki, it went to https://wiki.openssl.org/index.php/Binaries
for the binary dll but I tried the link https://indy.fulgan.com/SSL/ in
the w
On 18/04/18 12:15, wkitt...@windstream.net wrote:
On 04/17/2018 11:06 PM, James Richters wrote:> I have a whole section of
diagnostic writeln's in a program, and it's tedious to comment them all
out/in as needed. I'm curious if doing something like
what's wrong with traditional IFDEF?? use s
On 04/17/2018 11:06 PM, James Richters wrote:
I have a whole section of diagnostic writeln's in a program, and it's tedious
to comment them all out/in as needed. I'm curious if doing something like
what's wrong with traditional IFDEF?? use something like this...
{$IFDEF DEBUG}
writeln ('bl
Hi,
Why not define?
{$DEFINE DEBUG}
{$IFDEF DEBUG} Writeln('diagnostic info'); {$ENDIF}
V.
__
Od: "James Richters"
Komu: "'FPC-Pascal users discussions'"
Datum: 18.04.2018 05:06
Předmět: [fpc-pascal] Using constants instead o
Il 18/04/2018 05:06, James Richters ha scritto:
is there a better way to optionally exclude diagnostic information entirely
from the compiled program?
Did you consider to replace your Writeln with a DiagWrite (or whatever
name you prefer),
and have a DiagWrite such as:
DiagWrite: Procedu