>I use Git for just about any source code I work with.
I've just recently started using GIT, and have been using it for my own
applications. My solution until now has been to duplicate any units that
needed modification in with my source code so it would show up in my GIT
repository. But I li
I was waiting for the right time to also offer my sincere thanks to all
teams and individual contributors. I have been using fpc and Lazarus IDE
for quite some years now and I am very pleased with the constant
progress and improvement of these development tools. I have enjoyed
reading and learn
On 2017-06-15 22:17, James Richters wrote:
I specifically looked for agg_2d.pas (which is the one I was using)
I found that it also was fixed, but only 11 months ago... after 1.4.1
was released.
Yes, that's my bad. The agg_2d.pas unit was lagging behind for a while,
because I never really used
On 2017-06-15 15:06, James Richters wrote:
I don't like modifying units that are part of a package
because then I would need to remember how I modified them when a new
version is released or have to figure out what's going on all over
again.
I use Git for just about any source code I work with.
On 2017-06-15 13:34, Tomas Hajny wrote:
Not quite - the text-mode IDE doesn't invoke fpc.exe binary (it has the
compiler built-in) and it passes the options as defined in the respective
IDE dialogs.
Thanks Tomas for correcting me. I wasn't 100% sure about the behaviour
of a compiled-in compil
>And if you look in the "develop" branch of fpGUI, there is an even later
>AggPas version - last updated a month ago
I downloaded the fpGUI repository to have a look at it, and thought I would see
if any of the things I was encountering with it were addressed yet. Sure
enough, I found
{$IFDE
On Thu, June 15, 2017 16:06, James Richters wrote:
.
.
>> 3) Make sure you always rebuild the unit depending on the program you
>> want to compile (Compile -> Build).
>
> Is there a way to force this with the command line? (same as Compile >
> build from the IDE) ?
Yes, of course - it's the opti
On 15/06/17 17:45, Bernd Mueller wrote:
On 06/15/2017 10:34 AM, Mark Morgan Lloyd wrote:
Yes, but I was asking about the FPC situation. I'm desperately
resisting local pressure to write code that might end up non-trivial
in C/C++.
I realized a project with an ATTiny1634. Nothing special: I us
On 15/06/17 16:45, Karoly Balogh (Charlie/SGR) wrote:
Hi,
On Thu, 15 Jun 2017, Mark Morgan Lloyd wrote:
At the risk of making myself unpopular: because right now I /don't/ have> time.
Sorry, I didn't mean this personal to you. I was just a bit triggered onthe fact that
people offer competing p
>have you tried 30.0 as well? it looks like something needs a real number for
>this on the 64bit side...
I have just now tried 30.0 and it compiles and runs fine with x64.
I have also put the 30 back and changed the BYA and SYA variables to integers
and it also works fine on x64.
I just stuck
I have updated my unit for accessing parallel ports on Windows with Freepascal
to now select the correct .dll file depending on how the program is compiled.
It now uses
inpout32.dll if you compile for Win32
inpoutx64.dll if you compile for Win64
I also added a new sample program that can be
On 06/15/2017 08:20 AM, James Richters wrote:
Strangely:
LY:=Round(30.1-(BYA+SYA));
Also compiles fine with both Win32 and Win64
have you tried 30.0 as well? it looks like something needs a real number for
this on the 64bit side...
--
NOTE: No off-list assistance is given without prior ap
Hi,
On Thu, 15 Jun 2017, Mark Morgan Lloyd wrote:
> At the risk of making myself unpopular: because right now I /don't/ have
> time.
Sorry, I didn't mean this personal to you. I was just a bit triggered on
the fact that people offer competing products on FPC status requests,
because I've seen it
Thanks everyone for explaining this, and thanks for the various solutions. I
don't like modifying units that are part of a package because then I would need
to remember how I modified them when a new version is released or have to
figure out what's going on all over again.
> 3) Make sure yo
On Thu, 15 Jun 2017 07:57:14 -0400
"James Richters" wrote:
> >The idea is that you have one project per program. You can compile them
> >randomly without changing anything.
>
> I don't understand what you mean by 'one project per program' ?
Project is a Lazarus/msegui thing.
> I only have p
On Thu, June 15, 2017 13:57, James Richters wrote:
>>The idea is that you have one project per program. You can compile them
>> randomly without changing anything.
>
> I don't understand what you mean by 'one project per program' ? I only
> have programs that I have sorted in sub directories. I n
I have two almost identical programs, but one of them I cannot compile with
Win64, but it works fine with Win32.
I finally figured out that the difference between the two that seemed to
make a difference was the working one had constants defined, the one with
issues, those constants were changed
Am 15.06.2017 um 14:10 schrieb Mark Morgan Lloyd:
> On 15/06/17 11:30, Karoly Balogh (Charlie/SGR) wrote:
>> Hi,
>> On Thu, 15 Jun 2017, Mark Morgan Lloyd wrote:
mikroPascal (not free) supports AVR and many other chips.> >
https://shop.mikroe.com/compilers/mikropascal/avr-electronic-licen
On 15/06/17 11:30, Karoly Balogh (Charlie/SGR) wrote:
Hi,
On Thu, 15 Jun 2017, Mark Morgan Lloyd wrote:
mikroPascal (not free) supports AVR and many other chips.> >
https://shop.mikroe.com/compilers/mikropascal/avr-electronic-license> > Brian>> Yes, but
I was asking about the FPC situation. I'
>The idea is that you have one project per program. You can compile them
>randomly without changing anything.
I don't understand what you mean by 'one project per program' ? I only have
programs that I have sorted in sub directories. I normally use the Freepascal
text IDE to compile them, and
On 2017-06-15 11:37, James Richters wrote:
Maybe include Freetype32.dll and Freetype64.dll to make it very
clear.
That was exactly what I had in mind.
the program. Is there no way to set a global define in each program
so I could have several programs defined differently and randomly
compile
Hi,
On Thu, 15 Jun 2017, Mark Morgan Lloyd wrote:
> > mikroPascal (not free) supports AVR and many other chips.
> > https://shop.mikroe.com/compilers/mikropascal/avr-electronic-license
> > Brian
>
> Yes, but I was asking about the FPC situation. I'm desperately resisting
> local pressure to write
On 15/06/17 11:15, Rainer Stratmann wrote:
Am Donnerstag, 15. Juni 2017, 08:34:49 schrieb Mark Morgan Lloyd:> On 14/06/17 20:15, Brian wrote:>
> mikroPascal (not free) supports AVR and many other chips.> >
https://shop.mikroe.com/compilers/mikropascal/avr-electronic-license> > Brian> > Yes, but
Am Donnerstag, 15. Juni 2017, 08:34:49 schrieb Mark Morgan Lloyd:
> On 14/06/17 20:15, Brian wrote:
> > mikroPascal (not free) supports AVR and many other chips.
> > https://shop.mikroe.com/compilers/mikropascal/avr-electronic-license
> > Brian
>
> Yes, but I was asking about the FPC situation. I'
On Thu, 15 Jun 2017 06:37:41 -0400
"James Richters" wrote:
>[...]
> I see, thanks for explaining. For some reason, I was thinking it was
> optional to put it in the compiler, but I could also put it in the program.
> Is there no way to set a global define in each program so I could have
> sev
>True. I'll include a 64-bit version too.
That would be great, because I don't have a clue where this 64bit version I
found came from, what version it is, and things like that.
Maybe include Freetype32.dll and Freetype64.dll to make it very clear.
>That is why I said you must put it in your Pr
On 14/06/17 20:15, Brian wrote:
mikroPascal (not free) supports AVR and many other chips.
https://shop.mikroe.com/compilers/mikropascal/avr-electronic-license
Brian
Yes, but I was asking about the FPC situation. I'm desperately resisting
local pressure to write code that might end up non-trivi
On 2017-06-15 02:55, Stefan V. Pantazi wrote:
I think you need to use a global define passing a -d??? parameter
(-dAGG2D_USE_FREETYPE) to the compiler. Just adding it to a unit only
defines for that unit
The above statement is 100% correct.
Regards,
Graeme
--
fpGUI Toolkit - a cross-platf
On 2017-06-15 02:40, James Richters wrote:
That is what I thought should happen, but I put {$DEFINE
AGG2D_USE_FREETYPE}
I don't know why the define isn't making it to the unit. Do I need
to do something else?
Compiler defines defined with the $DEFINE directive is per unit only.
That is why I
29 matches
Mail list logo
