Op 09-01-19 om 18:27 schreef Martok via lazarus:
Lazbuild doesn't even have theoretical facilities to be a fppkg frontend (that
is, install the ide package), so that makes no sense at all. It's completely
unneeded for building - fpc finds its own fpc.cfg, therefore it would find the
units to us
Am 03.01.2019 um 00:31 schrieb Joost van der Sluis via lazarus:
> Should be fixed. In FPC (added the check if the compiler exists) and in
> Lazarus (do not choke on it when an exception occurs)
I just found out something else -- the exception also breaks Lazbuild, which,
since it doesn't have a G
Am 06.01.2019 um 21:11 schrieb Joost van der Sluis via lazarus:
> That's more a coincidence. Because all executables are installed into
> the same location.
For some values of "coincidence"...
On Windows, fpc lives in the Lazarus dir:
Lazarus\fpc\$FPCVer\bin\$HostCPU-$HostOS\
- fpc.exe
- fpmk
Op 06-01-19 om 17:29 schreef Martok via lazarus:
Am 03.01.2019 um 22:27 schrieb Joost van der Sluis via lazarus:
I actually don't know how to create the configuration files on Windows.
So, I checked the source, and it seems you actually do ;-)
Oh, I do know how to do it in code... (b.t.w. if
Am 03.01.2019 um 22:27 schrieb Joost van der Sluis via lazarus:
> I actually don't know how to create the configuration files on Windows.
So, I checked the source, and it seems you actually do ;-)
The Lazarus side generates a config if none is found (in a weird place, but that
is just GetAppConfig
Am 03.01.2019 um 22:27 schrieb Joost van der Sluis via lazarus:
> I actually don't know how to create the configuration files on Windows.
> (Except from letting Lazarus create them automatically based on the
> path, as described above. Or create them manually, or use fpcmkcfg...
> well... damn..
Op 03-01-19 om 21:17 schreef Martok via lazarus:
Am 03.01.2019 um 11:00 schrieb Joost van der Sluis via lazarus:
I build clean Lazarus (not even bigide) + FPC from trunk using fpclazup, start
it, and now receive a warning that wasn't there on last week's build. What steps
do I need to take to f
Am 03.01.2019 um 11:00 schrieb Joost van der Sluis via lazarus:
> The same holds if you remove gdb, make or the source-files of fpc's
> packages. While in principle Lazarus could be used without those.
Okay, now I feel even more confused than before...
I didn't remove anything?
I build clean La
Op 03-01-19 om 14:35 schreef Mattias Gaertner via lazarus:
On Thu, 3 Jan 2019 14:03:15 +0100
Joost van der Sluis via lazarus wrote:
There was no project yet that didn't need the fpc sources.
With pas2js this has changed. So this needs an ignore button now.
Are there any plans to make fppkg a
On Thu, 3 Jan 2019 14:03:15 +0100
Joost van der Sluis via lazarus wrote:
>[...]
> > If if it something I don't need then I would expect that it asks
> > only once and it can be disabled/uninstalled.
>
> When I remove fpc's sources, it will ask me again and again and
> again... See the response
Op 03-01-19 om 11:37 schreef Mattias Gaertner via lazarus:
On Thu, 3 Jan 2019 11:00:47 +0100
Joost van der Sluis via lazarus wrote:
[...]
This may be a stupid question, but why do I now have to click
through a message "An error occured during the initialization of
Fppkg: Could not find a fpc
On Thu, 3 Jan 2019 11:00:47 +0100
Joost van der Sluis via lazarus wrote:
>[...]
> > This may be a stupid question, but why do I now have to click
> > through a message "An error occured during the initialization of
> > Fppkg: Could not find a fpc executable in the PATH.
> > Check your Fppkg confi
On 03/01/2019 10:00, Joost van der Sluis via lazarus wrote:
"An error occured during the initialization of Fppkg: Could not find a
fpc
executable in the PATH.
Check your Fppkg configuration and restart Lazarus to be able to use
Fppkg's
functionality." ever time I start Lazarus?
I don't see t
On 02/01/2019 23:31, Joost van der Sluis via lazarus wrote:
Op 02-01-19 om 16:46 schreef C Western via lazarus:
To start the current lazarus trunk, I had to delete ~/.fppkg, as
otherwise lazarus crashed after trying to execute a compiler that
didn't exist. Traceback is:
[FORMS.PP] ExceptionOc
Op 03-01-19 om 03:23 schreef Martok via lazarus:
Am 03.01.2019 um 00:31 schrieb Joost van der Sluis via lazarus:
Should be fixed. In FPC (added the check if the compiler exists) and in
Lazarus (do not choke on it when an exception occurs)
This may be a stupid question, but why do I now have to
Am 03.01.2019 um 00:31 schrieb Joost van der Sluis via lazarus:
> Should be fixed. In FPC (added the check if the compiler exists) and in
> Lazarus (do not choke on it when an exception occurs)
This may be a stupid question, but why do I now have to click through a message
"An error occured durin
Op 02-01-19 om 16:46 schreef C Western via lazarus:
To start the current lazarus trunk, I had to delete ~/.fppkg, as
otherwise lazarus crashed after trying to execute a compiler that didn't
exist. Traceback is:
[FORMS.PP] ExceptionOccurred
Sender=EProcess
Exception=Executable not found:
On Wed, Jan 2, 2019 at 2:25 PM Werner Pamler via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> Am 02.01.2019 um 16:51 schrieb silvioprog via lazarus:
>
> The same problem here. In my case, 'Executable not found:
> "/home/silvioprog/fpc-3.0.4/lib/fpc/../../bin/fpc"'.
>
>
> Today I saw the "Coul
Am 02.01.2019 um 16:51 schrieb silvioprog via lazarus:
The same problem here. In my case, 'Executable not found:
"/home/silvioprog/fpc-3.0.4/lib/fpc/../../bin/fpc"'.
Today I saw the "Could not find a fpc executable in the PATH" error when
starting Lazarus. It came in in r59934, the preceding
On Wed, Jan 2, 2019 at 12:46 PM C Western via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> To start the current lazarus trunk, I had to delete ~/.fppkg, as
> otherwise lazarus crashed after trying to execute a compiler that didn't
> exist. Traceback is:
>
> [FORMS.PP] ExceptionOccurred
>S
To start the current lazarus trunk, I had to delete ~/.fppkg, as
otherwise lazarus crashed after trying to execute a compiler that didn't
exist. Traceback is:
[FORMS.PP] ExceptionOccurred
Sender=EProcess
Exception=Executable not found:
"/home/me/fpc-3.0.2-64/lib/fpc/../../bin/fpc"
Stack
21 matches
Mail list logo
