On Mon, 17 Feb 2014 17:09:17 +0200
patspiper wrote:
> On 17/02/14 16:45, Mattias Gaertner wrote:
> > On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
> > Michael Van Canneyt wrote:
> >
> >> On Mon, 17 Feb 2014, Mattias Gaertner wrote:
> >> [...]
> >>> Is there already a doc about how to install multiple
On Mon, February 17, 2014 21:02, patspiper wrote:
> On 17/02/14 21:41, Sven Barth wrote:
>> On 17.02.2014 17:56, patspiper wrote:
>>> On a side note, for 2.7.1, 'fpc -h' shows the -V and -Xp options
>>> whereas
>>> 'fpc' alone (requires the pressing of to view successive pages)
>>> does not.
>>
>>
On 17 Feb 2014, at 10:34, Mattias Gaertner wrote:
> On Mon, 17 Feb 2014 00:02:11 +0100
> Ewald wrote:
>
>> [...]
>>
>> I'm not sure if that is really what you need, but I think this is the most
>> flexible/straightforward method of `running one fpc.cfg per fpc version`.
>
> It is the most fle
On 17/02/14 21:41, Sven Barth wrote:
On 17.02.2014 17:56, patspiper wrote:
On a side note, for 2.7.1, 'fpc -h' shows the -V and -Xp options whereas
'fpc' alone (requires the pressing of to view successive pages)
does not.
Are you sure that fpc is picking up the correct ppcX (help output is
a
On 17.02.2014 17:56, patspiper wrote:
On a side note, for 2.7.1, 'fpc -h' shows the -V and -Xp options whereas
'fpc' alone (requires the pressing of to view successive pages)
does not.
Are you sure that fpc is picking up the correct ppcX (help output is
always generated by the ppcX)? Because
On 17.02.2014 13:24, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 12:41:45 +0100
Sven Barth wrote:
Am 17.02.2014 12:16 schrieb "Mattias Gaertner" :
What more do you need ?
I'm investigating what Lazarus needs to support to switch fpc versions
more easily. That's why I'm collecting all the po
On Mon, 17 Feb 2014, Tomas Hajny wrote:
On Mon, February 17, 2014 17:37, Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, Tomas Hajny wrote:
I agree that the best option would be to use the -V and -P options of
fpc.
But, for this, it would be best if fpc can list the available versions
and
On Mon, February 17, 2014 17:37, Michael Van Canneyt wrote:
> On Mon, 17 Feb 2014, Tomas Hajny wrote:
>
>>> I agree that the best option would be to use the -V and -P options of
>>> fpc.
>>>
>>> But, for this, it would be best if fpc can list the available versions
>>> and
>>> architectures/cross-c
On 17/02/14 18:26, Tomas Hajny wrote:
On Mon, February 17, 2014 16:13, Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, patspiper wrote:
On 17/02/14 16:45, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
On 17/02/14 17:53, Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, patspiper wrote:
On 17/02/14 17:13, Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, patspiper wrote:
On 17/02/14 16:45, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
Michael Van Canneyt wrote:
On Mo
In our previous episode, Michael Van Canneyt said:
>
> -Xp is there for the case you have a special setup.
>
> -V is there for standard installations, so you don't need to know the paths.
>
> I think it is by far preferable to use the latter.
> If you're not going to use/encourage it, you'd bett
On Mon, 17 Feb 2014, Tomas Hajny wrote:
I agree that the best option would be to use the -V and -P options of fpc.
But, for this, it would be best if fpc can list the available versions and
architectures/cross-compilers.
Assuming that list of supported FPC installations should be configura
On Mon, February 17, 2014 16:13, Michael Van Canneyt wrote:
> On Mon, 17 Feb 2014, patspiper wrote:
>> On 17/02/14 16:45, Mattias Gaertner wrote:
>>> On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
>>> Michael Van Canneyt wrote:
>>>
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
[...]
> Is th
On Mon, February 17, 2014 16:53, Michael Van Canneyt wrote:
> On Mon, 17 Feb 2014, patspiper wrote:
>> On 17/02/14 17:13, Michael Van Canneyt wrote:
>>> On Mon, 17 Feb 2014, patspiper wrote:
>>>
On 17/02/14 16:45, Mattias Gaertner wrote:
> On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
> Mic
On Mon, 17 Feb 2014, patspiper wrote:
On 17/02/14 17:13, Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, patspiper wrote:
On 17/02/14 16:45, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
[...]
On 17/02/14 17:13, Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, patspiper wrote:
On 17/02/14 16:45, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
[...]
Is there already a doc about how to instal
On Mon, 17 Feb 2014, patspiper wrote:
On 17/02/14 16:45, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
[...]
Is there already a doc about how to install multiple versions of fpc?
No, because
a) The
On 17/02/14 16:45, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
Michael Van Canneyt wrote:
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
[...]
Is there already a doc about how to install multiple versions of fpc?
No, because
a) There are so many ways to do it
b) There are
In our previous episode, Mattias Gaertner said:
> > I do think we can certainly make the default behaviour more 'version aware'
> > by installing
> > a config file that already implements one of the different schemes.
> >
> > That said, I am still not convinced of the need for this, I work since
On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
Michael Van Canneyt wrote:
> On Mon, 17 Feb 2014, Mattias Gaertner wrote:
>[...]
> > Is there already a doc about how to install multiple versions of fpc?
>
> No, because
> a) There are so many ways to do it
> b) There are so many platforms.
> I prefer to
On Mon, February 17, 2014 15:15, Mattias Gaertner wrote:
> On Mon, 17 Feb 2014 14:14:03 +0100
> "Tomas Hajny" wrote:
.
.
>> Still, my open question is: what are the drivers for needing to support
>> (=
>> having to maintain) different fpc.cfg files for different FPC versions?
>> Moreover - if pe
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
My dream:
User installed some FPC versions, Lazarus finds all available versions
and user can choose from the list. If it is not in the list, the user
selects once the new compiler and Lazarus adds it to the list.
At least that should be possible
On Mon, 17 Feb 2014 14:14:03 +0100
"Tomas Hajny" wrote:
>[...]
> I guess that it's at least partly also due to different needs and
> preferences of different people. If I use one FPC version most of the time
> and only want to keep older versions for occassional regression testing, I
> do not nee
On Mon, 17 Feb 2014, Mattias Gaertner wrote:
On Mon, 17 Feb 2014 10:50:02 +0100 (CET)
Michael Van Canneyt wrote:
[...]
You can perfectly cater for different FPC versions in 1 config file.
It has support for ifdef, include and whatnot.
You can probably even have (I would need to check this)
On Mon, February 17, 2014 13:24, Mattias Gaertner wrote:
.
.
>> > I'm investigating what Lazarus needs to support to switch fpc versions
>> > more easily. That's why I'm collecting all the possibilities how
>> people
>> > install multiple versions of fpc. I'm puzzled of the amount of
>> differen
On Mon, 17 Feb 2014 12:41:45 +0100
Sven Barth wrote:
> Am 17.02.2014 12:16 schrieb "Mattias Gaertner" :
> > > What more do you need ?
> >
> > I'm investigating what Lazarus needs to support to switch fpc versions
> > more easily. That's why I'm collecting all the possibilities how people
> > inst
On Mon, February 17, 2014 12:15, Mattias Gaertner wrote:
> On Mon, 17 Feb 2014 10:50:02 +0100 (CET)
> Michael Van Canneyt wrote:
>
>>[...]
>> You can perfectly cater for different FPC versions in 1 config file.
>> It has support for ifdef, include and whatnot.
>> You can probably even have (I woul
Am 17.02.2014 12:16 schrieb "Mattias Gaertner" :
> > What more do you need ?
>
> I'm investigating what Lazarus needs to support to switch fpc versions
> more easily. That's why I'm collecting all the possibilities how people
> install multiple versions of fpc. I'm puzzled of the amount of differen
On Mon, 17 Feb 2014 10:50:02 +0100 (CET)
Michael Van Canneyt wrote:
>[...]
> You can perfectly cater for different FPC versions in 1 config file.
> It has support for ifdef, include and whatnot.
> You can probably even have (I would need to check this)
>
> #include /etc/fpc.d/$FPCVERSION$.cfg
N
In our previous episode, Mattias Gaertner said:
>
> My point is:
> The current search ../etc/fpc.cfg does not work with the
> current defaults of "make install". The following would be better:
(I missed this earlier). It is /geared/ towards multiple "make install".
Just not "make install" into th
On Mon, 17 Feb 2014 10:36:21 +0100 (CET)
mar...@stack.nl (Marco van de Voort) wrote:
>[...]
> And none of all address the duplication of binaries in the bin directories.
True.
Mattias
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://l
On Mon, 17 Feb 2014, Marco van de Voort wrote:
In our previous episode, Mattias Gaertner said:
I'm not sure if that is really what you need, but I think this is the most
flexible/straightforward method of `running one fpc.cfg per fpc version`.
It is the most flexible, I agree with that.
M
In our previous episode, Mattias Gaertner said:
> >
> > I'm not sure if that is really what you need, but I think this is the most
> > flexible/straightforward method of `running one fpc.cfg per fpc version`.
>
> It is the most flexible, I agree with that.
>
> Most straightforward:
> Without the
On Mon, 17 Feb 2014 00:02:11 +0100
Ewald wrote:
>[...]
> The trick is basically to run fpc with two switches, and a modified $PATH:
> - [-n]: One that disables the default config file
> - [@XXX]: One that specifies where to look for the config file. (as
> the quoted text states this sho
On Sun, 16 Feb 2014 19:14:33 +0100, Mattias
Gaertner wrote:
>
> Yes, for example make install INSTALL_PREFIX=~/2.6.2 installs to
> ~/2.6.2/lib/fpc/2.6.2
> Which looks odd.
>
> Maybe fpc should search for /fpc.cfg.
>
> Then maybe the current search for /../etc/fpc.cfg can be
> removed. Only a few
In our previous episode, Florian Kl?mpfl said:
> > I don't think it was ever meant for distribution conforming installs, since
> > they don't carter for multiversion systems.
>
> You can also have easily different gcc versions at least on linux.
Yes. But then this whole discussion is useless, sin
Am 16.02.2014 19:46, schrieb Marco van de Voort:
> In our previous episode, Mattias Gaertner said:
>>> I played with this in 1.9.2 times iirc.
>>>
>>> IIRC the principle was developed for cases where every version installed
>>> into a prefix with make INSTALL INSTALL_PREFIX=~/somethingversion. (s
In our previous episode, Mattias Gaertner said:
> > I played with this in 1.9.2 times iirc.
> >
> > IIRC the principle was developed for cases where every version installed
> > into a prefix with make INSTALL INSTALL_PREFIX=~/somethingversion. (so that
> > you also had multiple bin directories a
Why not fpc-$FPCVERSION.cfg? And keep them all in /etc/ ? fpc-2.6.2.cfg,
and fpc-2.7.1.cfg, etc.
This way fpc will use it's version and search for the right one in a
standard directory?
- Dennis Fehr
On 14-02-16 12:14 PM, Mattias Gaertner wrote:
On Sun, 16 Feb 2014 15:28:59 +0100 (CET)
mar...
On Sun, 16 Feb 2014 13:29:42 +0100
"Tomas Hajny" wrote:
>[...]
> If having different file per version is really necessary (rather than only
> having differences among versions covered by #IFDEF within a single file),
> combining an #IFDEF with an #INCLUDE inside the fpc.cfg may be an option.
> Re
On Sun, 16 Feb 2014 15:28:59 +0100 (CET)
mar...@stack.nl (Marco van de Voort) wrote:
>[...]
> I played with this in 1.9.2 times iirc.
>
> IIRC the principle was developed for cases where every version installed
> into a prefix with make INSTALL INSTALL_PREFIX=~/somethingversion. (so that
> you
On Sun, 16 Feb 2014 12:00:59 +
Mark Morgan Lloyd wrote:
>[...]
> I've got a very vague recollection from elsewhere that you can do this
> sort of thing using a unix-domain (named) pipe. In other words it would
> probably be something like a "config-file server" daemon listening for
> attem
On 16/02/14 16:28, Marco van de Voort wrote:
In our previous episode, Mattias Gaertner said:
The second is actually
/../etc/fpc.cfg
So, fpc first searches a user config, then a "flavor" config (e.g. one
per version) and the last is the global config.
When installing multiple version of fpc you
In our previous episode, Mattias Gaertner said:
> The second is actually
> /../etc/fpc.cfg
>
> So, fpc first searches a user config, then a "flavor" config (e.g. one
> per version) and the last is the global config.
>
> When installing multiple version of fpc you normally get
> /usr/(local/)lib/f
On Sun, February 16, 2014 13:00, Mark Morgan Lloyd wrote:
> Mattias Gaertner wrote:
>> Hi,
>>
>> Is there a recommended or usual way to install multiple FPC versions
>> and one fpc.cfg per version under Linux/Unix?
>>
>> fpc 2.6.2 and 2.7.1 search fpc.cfg under Linux:
>>
>> Configfile search: /home
Mattias Gaertner wrote:
Hi,
Is there a recommended or usual way to install multiple FPC versions
and one fpc.cfg per version under Linux/Unix?
fpc 2.6.2 and 2.7.1 search fpc.cfg under Linux:
Configfile search: /home/mattias/.fpc.cfg
Configfile search: /usr/lib/fpc/etc/fpc.cfg
Configfile search
On Sun, 16 Feb 2014 01:53:16 +0100
Mattias Gaertner wrote:
>[...]
> When installing multiple version of fpc you normally get
> /usr/(local/)lib/fpc/2.6.2/ppcx86
> /usr/(local/)lib/fpc/2.7.1/ppcx86
s/x86/x64/
Mattias
___
fpc-devel maillist - fpc-dev
Hi,
Is there a recommended or usual way to install multiple FPC versions
and one fpc.cfg per version under Linux/Unix?
fpc 2.6.2 and 2.7.1 search fpc.cfg under Linux:
Configfile search: /home/mattias/.fpc.cfg
Configfile search: /usr/lib/fpc/etc/fpc.cfg
Configfile search: /etc/fpc.cfg
The second
48 matches
Mail list logo
