On 2014-04-04 15:32, Henry Vermaak wrote:
>
> I use -vi-n-h- for my release builds, which removes info, notes and
> hints, otherwise it becomes hard to see the wood from the trees!
Exactly what I want to try and do, but it seems FPC is really stubborn
under FreeBSD. I tried the exact same -v para
On Fri, 4 Apr 2014, Graeme Geldenhuys wrote:
On 2014-04-04 15:32, Henry Vermaak wrote:
I use -vi-n-h- for my release builds, which removes info, notes and
hints, otherwise it becomes hard to see the wood from the trees!
Exactly what I want to try and do, but it seems FPC is really stubborn
On 2014-04-05 11:48, Michael Van Canneyt wrote:
>
> maybe it's loading some config file anyway.
> Do a strace and see if it opens a config file.
'strace' is not available/supported by 64-bit FreeBSD (only 32-bit
FreeBSD). But I did remember that FPC has a very verbose output option.
Amazingly tha
On 05/04/14 13:29, Graeme Geldenhuys wrote:
That is the only config file it found and loaded. That config file
contains a -v- option, but even removing that option completely makes no
difference.
-v- doesn't do anything, it's -v0 that should switch off all output
(except for errors and fatal e
Hi Graeme,
maybe you should do a
a
$FPC -va -h | grep "Reading options from"
and check which configuration file is loaded.
But anyhow, the option unit contains code that
normally ensure that command line options always
win over config file options.
However, Michael is right in asking ab
In our previous episode, Graeme Geldenhuys said:
> > maybe it's loading some config file anyway.
> > Do a strace and see if it opens a config file.
>
> 'strace' is not available/supported by 64-bit FreeBSD (only 32-bit
> FreeBSD).
That's because it is a port. The normal tool to use on BSDs is k
On 2014-04-05 13:07, Jonas Maebe wrote:
>
> -v- doesn't do anything, it's -v0 that should switch off all output
> (except for errors and fatal errors).
Thanks. So what is the difference between -ve and -v0? From the compiler
help output it sounds like they do the same thing. But neither of them
On 2014-04-05 13:36, Marco van de Voort wrote:
> I doubt it, filtering log output isn't really platform dependent.
That is what I assume too. So the issue is probably across all platforms
then (but I haven't tested elsewhere yet).
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI
El 04/04/14 17:46, Krzysztof ha escrit:
> Hi,
>
> DBus documentation give me a headache. Does anyone know solution how
> to implement DBus in GUI main loop (for signals listening)? I have
> tried with threads but have two problems:
> 1. Not all signals are catched (randomly)
> 2. Deadlock when mai
On 2014-04-05 13:09, Pierre Free Pascal wrote:
> $FPC -va -h | grep "Reading options from"
> and check which configuration file is loaded.
That is pretty much what I did...
--
[freebsd (tiopf2)]$ fpc -va -h | grep "Reading options from"
[0.000] Reading options from file /home/
On 05/04/14 15:11, Graeme Geldenhuys wrote:
On 2014-04-05 13:07, Jonas Maebe wrote:
>
>-v- doesn't do anything, it's -v0 that should switch off all output
>(except for errors and fatal errors).
Thanks. So what is the difference between -ve and -v0?
-ve does not switch anything off, it only en
On Sat, 5 Apr 2014, Jonas Maebe wrote:
On 05/04/14 15:11, Graeme Geldenhuys wrote:
On 2014-04-05 13:07, Jonas Maebe wrote:
>
>-v- doesn't do anything, it's -v0 that should switch off all output
>(except for errors and fatal errors).
Thanks. So what is the difference between -ve and -v0?
-
On 05.04.2014 15:18, Graeme Geldenhuys wrote:
On 2014-04-05 13:09, Pierre Free Pascal wrote:
$FPC -va -h | grep "Reading options from"
and check which configuration file is loaded.
That is pretty much what I did...
--
[freebsd (tiopf2)]$ fpc -va -h | grep "Reading options
On Sat, April 5, 2014 17:26, Michael Van Canneyt wrote:
>
>
> On Sat, 5 Apr 2014, Jonas Maebe wrote:
>
>> On 05/04/14 15:11, Graeme Geldenhuys wrote:
>>> On 2014-04-05 13:07, Jonas Maebe wrote:
>
>-v- doesn't do anything, it's -v0 that should switch off all output
>(except for errors
On 2014-04-05 16:23, Jonas Maebe wrote:
>
> -ve does not switch anything off, it only enables showing errors
Ah, now I understand. Thanks for the info.
For an immediate solution (work-around), I enabled message numbers
(-vq), and then created a long list of -vm[x],[y] options to suppress
the mes
On 2014-04-05 17:00, Sven Barth wrote:
>
> Could you test by disabling the usage of a config file (-n)? You'll need
> to pass all paths using -Fu then,
No problem. Just did the test with -n and it made no difference when it
comes to the -v parameter options. The -vh- , -vw- and -v0 parameters
ar
On Sat, April 5, 2014 21:13, Graeme Geldenhuys wrote:
> On 2014-04-05 17:00, Sven Barth wrote:
>>
>> Could you test by disabling the usage of a config file (-n)? You'll need
>> to pass all paths using -Fu then,
>
> No problem. Just did the test with -n and it made no difference when it
> comes to t
17 matches
Mail list logo
