Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-other / 2010-09

Re: Parallel processing in the compiler

13 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Florian Klaempfl
Graeme Geldenhuys wrote 5 lines
On 6 September 2010 10:04, Florian Klaempfl wrote: > > Yes, I forgot that you don't like easy to use software. I'm using FPC and Lazarus, aren't I? ;-)

Indeed, rather strange ...

Show quoted text 6 lines
> Oh really? Strangly enough other software works fine on my system :) Nothing strange really. Windows behaviour is so random, nobody can predict how Windows will behave next.

At least it behaves, other OSes misbehave ;)

Show quoted text 8 lines
> Sometimes one can guess from the look of a software (yes, git gui looks > poor) on its quality. You should know the old saying: Don't judge a book my it's cover. Have you ever seen cad engineering software

And even there is applies. CATIA, one of the top cad systems, looks very nice.

or machine control/monitor software. They all look pretty crap to me (UI interface), yet with the correct person driving those software, it works like a dream to them.

Yes, I know this kind of software: only if you know all its pitfalls and avoid them, you can use it like a dream and that's what I call crap.

Anyway Florian, nice to see I'm off your "junk mail" filter. ;-)

You're only filtered directly to "FPC gelesen" for a few weeks already, sometimes I look through it :)

Graeme Geldenhuys
Henry Vermaak wrote
The install is crazy, it basically installs a whole mingw/msys system (when I last checked).  I've already got an mingw/msys install and having two is suicide.  I've heard that people use the git install as a base and then install other mingw/msys packages on top of it.

No idea which Windows git version you are running. There is the old Cygwin version, and the newer (windows native) msysGit version. The latter is a mere 12MB download, and allows install customization on how it should integrate with Windows, and how it should handle LineEnding characters etc. Nothing difficult about it, and the tools included work just fine.

Saying that, my Windows usage is limited these days. For the last few years, most of my time spent developing software is under Linux. But we do test our software and do bug fixing under Windows, in a VirtualBox session. In such cases I do use msysGit (last installed version is 1.6.2.1 from 2009-03), and found none of the issues Florian raised. I have a cloned copy of FPC & Lazarus git mirrors, and of our company software repositories all setup in the VM session. A stand-alone development VM environment. Maybe I'm just lucky, or Windows behaves better in a limited VM environment. Who knows? :-)

Regards,   - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/
Henry Vermaak
to Graeme Geldenhuys
Graeme Geldenhuys wrote 13 lines
On 6 September 2010 10:27, Henry Vermaak wrote: > The install is crazy, it basically installs a whole mingw/msys system > (when I last checked).  I've already got an mingw/msys install and > having two is suicide.  I've heard that people use the git install as > a base and then install other mingw/msys packages on top of it. No idea which Windows git version you are running. There is the old Cygwin version, and the newer (windows native) msysGit version. The latter is a mere 12MB download, and allows install customization on how it should integrate with Windows, and how it should handle LineEnding characters etc.  Nothing difficult about it, and the tools included work just fine.

Yes, I'm talking about msysgit. It installs a whole msys tree, which I am not interested in, as I've explained above. Perhaps I'll try and build git inside my own msys. I have no idea why they just didn't integrate it - I'm sure there must be a reason.

Henry

Florian Klaempfl
to Graeme Geldenhuys: No idea which Windows git version you are running. There is the old Cygwin version, and…
Graeme Geldenhuys wrote 6 lines
Saying that, my Windows usage is limited these days. For the last few years, most of my time spent developing software is under Linux. But we do test our software and do bug fixing under Windows, in a VirtualBox session. In such cases I do use msysGit (last installed version is 1.6.2.1 from 2009-03), and found none of the issues Florian raised.

git command line works for me as well under Linux in a Virtual Box ;) But that's not what I want :)

Marco van de Voort
to Henry Vermaak: Yes, I'm talking about msysgit. It installs a whole msys tree, which I am not interested…

In our previous episode, Henry Vermaak said:

Show quoted text 8 lines
> how it should integrate with Windows, and how it should handle > LineEnding characters etc. ?Nothing difficult about it, and the tools > included work just fine. Yes, I'm talking about msysgit. It installs a whole msys tree, which I am not interested in, as I've explained above. Perhaps I'll try and build git inside my own msys. I have no idea why they just didn't integrate it - I'm sure there must be a reason.

Afaik, like cywin, msys has also started with keeping a global state. It might be possible that recent builds of GIT have problems with installing multiple versions (or just moving them), while olders (that Graeme uses) didn't.

Sven Barth
to Henry Vermaak: Yes, I'm talking about msysgit. It installs a whole msys tree, which I am not interested…
Henry Vermaak wrote
Yes, I'm talking about msysgit. It installs a whole msys tree, which I am not interested in, as I've explained above. Perhaps I'll try and build git inside my own msys. I have no idea why they just didn't integrate it - I'm sure there must be a reason.

It simplifies installation. They might have come to the conclusion that most users that want to use Git don't have a msys installation. And msys is needed for the tools and environment that Git relies on.

I personally prefer it this way, because for all other tasks that are better done with Unix tools I use the POSIX subsystem (Interix, SFU, SUA) that comes with Windows :)

Regards,
Sven

Henry Vermaak
to Sven Barth
Sven Barth wrote 10 lines
Am 06.09.2010 11:29, schrieb Henry Vermaak: > > Yes, I'm talking about msysgit.  It installs a whole msys tree, which > I am not interested in, as I've explained above.  Perhaps I'll try and > build git inside my own msys.  I have no idea why they just didn't > integrate it - I'm sure there must be a reason. It simplifies installation. They might have come to the conclusion that most users that want to use Git don't have a msys installation. And msys is needed for the tools and environment that Git relies on.

Obviously.

The problem, as I've stated previously, is that (imo) having two different mingw/msys installations on the path would be asking for trouble (different versions of gcc, libs, etc). That's why some people start with the git install, then unzip extra packages into that directory when they need them. Hopefully with the new mingw-get there will be a package for git in time.

Henry

Sven Barth
to Henry Vermaak
Henry Vermaak wrote 6 lines
The problem, as I've stated previously, is that (imo) having two different mingw/msys installations on the path would be asking for trouble (different versions of gcc, libs, etc). That's why some people start with the git install, then unzip extra packages into that directory when they need them. Hopefully with the new mingw-get there will be a package for git in time.

At least in my installation (I've set Git to be run in Cmd (or PowerShell in my case)) only the directory that contains the cmd wrappers (%GitInstallDir%\cmd) is in the PATH. And as that directory only contains that wrappers it might set up its environment on start by itself. Thus it should not conflict with other msys installations.

Regards,
Sven

Henry Vermaak
to Sven Barth
Sven Barth wrote 14 lines
Am 06.09.2010 13:46, schrieb Henry Vermaak: > > The problem, as I've stated previously, is that (imo) having two > different mingw/msys installations on the path would be asking for > trouble (different versions of gcc, libs, etc).  That's why some > people start with the git install, then unzip extra packages into that > directory when they need them.  Hopefully with the new mingw-get there > will be a package for git in time. At least in my installation (I've set Git to be run in Cmd (or PowerShell in my case)) only the directory that contains the cmd wrappers (%GitInstallDir%\cmd) is in the PATH. And as that directory only contains that wrappers it might set up its environment on start by itself. Thus it should not conflict with other msys installations.

Perhaps it'll work o.k. then.

Henry

Florian Klaempfl
to Henry Vermaak: Obviously. The problem, as I've stated previously, is that (imo) having two different…
Henry Vermaak wrote 20 lines
On 6 September 2010 12:21, Sven Barth wrote: > Am 06.09.2010 11:29, schrieb Henry Vermaak: >> >> Yes, I'm talking about msysgit. It installs a whole msys tree, which >> I am not interested in, as I've explained above. Perhaps I'll try and >> build git inside my own msys. I have no idea why they just didn't >> integrate it - I'm sure there must be a reason. > > It simplifies installation. They might have come to the conclusion that most > users that want to use Git don't have a msys installation. And msys is > needed for the tools and environment that Git relies on. Obviously. The problem, as I've stated previously, is that (imo) having two different mingw/msys installations on the path would be asking for trouble (different versions of gcc, libs, etc). That's why some people start with the git install, then unzip extra packages into that directory when they need them. Hopefully with the new mingw-get there will be a package for git in time.

IIRC breaks msys git in the path (even as last entry) even FPC building :) So a no-go :)

Henry Vermaak
to Florian Klaempfl
Florian Klaempfl wrote 24 lines
Am 06.09.2010 13:46, schrieb Henry Vermaak: > On 6 September 2010 12:21, Sven Barth wrote: >> Am 06.09.2010 11:29, schrieb Henry Vermaak: >>> >>> Yes, I'm talking about msysgit.  It installs a whole msys tree, which >>> I am not interested in, as I've explained above.  Perhaps I'll try and >>> build git inside my own msys.  I have no idea why they just didn't >>> integrate it - I'm sure there must be a reason. >> >> It simplifies installation. They might have come to the conclusion that most >> users that want to use Git don't have a msys installation. And msys is >> needed for the tools and environment that Git relies on. > > Obviously. > > The problem, as I've stated previously, is that (imo) having two > different mingw/msys installations on the path would be asking for > trouble (different versions of gcc, libs, etc).  That's why some > people start with the git install, then unzip extra packages into that > directory when they need them.  Hopefully with the new mingw-get there > will be a package for git in time. IIRC breaks msys git in the path (even as last entry) even FPC building :) So a no-go :)

Hmm, I can't build fpc under msys anyway, have you managed to do this?

Henry

Sven Barth
to Florian Klaempfl: IIRC breaks msys git in the path (even as last entry) even FPC building :) So a no-go :)
Florian Klaempfl wrote 24 lines
Am 06.09.2010 13:46, schrieb Henry Vermaak: > On 6 September 2010 12:21, Sven Barth wrote: >> Am 06.09.2010 11:29, schrieb Henry Vermaak: >>> >>> Yes, I'm talking about msysgit. It installs a whole msys tree, which >>> I am not interested in, as I've explained above. Perhaps I'll try and >>> build git inside my own msys. I have no idea why they just didn't >>> integrate it - I'm sure there must be a reason. >> >> It simplifies installation. They might have come to the conclusion that most >> users that want to use Git don't have a msys installation. And msys is >> needed for the tools and environment that Git relies on. > > Obviously. > > The problem, as I've stated previously, is that (imo) having two > different mingw/msys installations on the path would be asking for > trouble (different versions of gcc, libs, etc). That's why some > people start with the git install, then unzip extra packages into that > directory when they need them. Hopefully with the new mingw-get there > will be a package for git in time. IIRC breaks msys git in the path (even as last entry) even FPC building :) So a no-go :)

If I remember correctly the msysGit setup provides multiple ways of setting up the PATH variable. Might be that I chose the safest option, because I have no troubles building FPC :)

Regards,
Sven

Henry Vermaak
to Henry Vermaak: Hmm, I can't build fpc under msys anyway, have you managed to do this? Henry
Henry Vermaak wrote 27 lines
On 8 September 2010 13:35, Florian Klaempfl wrote: > Am 06.09.2010 13:46, schrieb Henry Vermaak: >> On 6 September 2010 12:21, Sven Barth wrote: >>> Am 06.09.2010 11:29, schrieb Henry Vermaak: >>>> >>>> Yes, I'm talking about msysgit.  It installs a whole msys tree, which >>>> I am not interested in, as I've explained above.  Perhaps I'll try and >>>> build git inside my own msys.  I have no idea why they just didn't >>>> integrate it - I'm sure there must be a reason. >>> >>> It simplifies installation. They might have come to the conclusion that most >>> users that want to use Git don't have a msys installation. And msys is >>> needed for the tools and environment that Git relies on. >> >> Obviously. >> >> The problem, as I've stated previously, is that (imo) having two >> different mingw/msys installations on the path would be asking for >> trouble (different versions of gcc, libs, etc).  That's why some >> people start with the git install, then unzip extra packages into that >> directory when they need them.  Hopefully with the new mingw-get there >> will be a package for git in time. > > IIRC breaks msys git in the path (even as last entry) even FPC building > :) So a no-go :) Hmm, I can't build fpc under msys anyway, have you managed to do this?

I think the reason for this is the different path separators.

Henry