Sign in Join

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

Mailing lists / lazarus / 2008-12

Cross platform development (not compiling)

9 messages · 6 people · –

Reply by email Subscribe to this list Your subscription

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

Reenen Laurie

When I work cross platform (develop at home on linux, and at work on windows), I have to have separate .lpi / lpr files for linux and windows...

My assumption is that this line in the windows (lpi) version makes it not work:
<RunParams>
<local>
<FormatVersion Value="1"/>
<LaunchingApplication PathPlusParams="/usr/X11R6/bin/xterm -T 'Lazarus Run Output' -e $(LazarusDir)/tools/runwait.sh $(TargetCmdLine)"/> </local>
</RunParams>

Obviously that's not windows...

Do all of you have to keep a <project_win> and <project_lin> .lpi and lpr ?

o__ ,_.>/ _ (_)_\(_)_______ ...speed is good _______________ I believe five out of four people have a problem with fractions. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.lazarus.freepascal.org/pipermail/lazarus/attachments/20081209/737463bf/attachment.html

Reply by email

Marc Weustink
to Mattias Gärtner: An embedded and charset-unspecified text was scrubbed... Name: not available Url:…
Mattias G?rtner wrote 24 lines
Zitat von Reenen Laurie : > When I work cross platform (develop at home on linux, and at work on > windows), I have to have separate .lpi / lpr files for linux and windows... > > My assumption is that this line in the windows (lpi) version makes it not > work: > <RunParams> > <local> > <FormatVersion Value="1"/> > <LaunchingApplication PathPlusParams="/usr/X11R6/bin/xterm -T > 'Lazarus Run Output' -e $(LazarusDir)/tools/runwait.sh $(TargetCmdLine)"/> > </local> > </RunParams> > > Obviously that's not windows... > > Do all of you have to keep a <project_win> and <project_lin> .lpi and lpr ? No. I only have one lpi and lpr per project. But I don't use launching application. Maybe launchingapplication should be moved to lps? Marc can tell.

Who me ?

There are ideas to move some debugger options to project specifics. Anyway, I use 2 different .lpi files (one is a copy of another) to cross develop for win32 and wince, since I need to swap targetcpu and targetos So moving launchingapplication itself is not enough

Marc

Reply by email

Felipe Monteiro de Carvalho
to Mattias Gärtner
Mattias G?rtner wrote
build modes are only for compilation. Not for debugging. Maybe you want debug modes?

Ummm, now I see ... but they could be the same thing. Some kind of mode where certain compiler options or debugger options are overriden.

Felipe Monteiro de Carvalho

Reply by email

Graeme Geldenhuys
to Felipe Monteiro de Carvalho

On Tue, Dec 9, 2008 at 7:33 PM, Felipe Monteiro de Carvalho >

Ummm, now I see ... but they could be the same thing. Some kind of mode where certain compiler options or debugger options are overriden.

That would be very handy! MSEide has a very simple design/screen for this. And it works very well.

The "Project" menu contains the following options: Make
Build
Make 1
Make 2
Make 3
Make 4

You can setup each of those with the following screen. See attached image. Simply add a new row, tick which Build or Make it should apply to, and select the menu from the Project menu.

Quick, Easy and Effective!

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mseide.png
Type: image/png
Size: 4279 bytes
Desc: not available
Url : http://www.lazarus.freepascal.org/pipermail/lazarus/attachments/20081210/853e3841/attachment-0001.png

Reply by email

Mattias Gaertner
to Graeme Geldenhuys
Show quoted text 21 lines
On Tue, Dec 9, 2008 at 7:33 PM, Felipe Monteiro de Carvalho > > Ummm, now I see ... but they could be the same thing. Some kind of > mode where certain compiler options or debugger options are > overriden. That would be very handy! MSEide has a very simple design/screen for this. And it works very well. The "Project" menu contains the following options: Make Build Make 1 Make 2 Make 3 Make 4 You can setup each of those with the following screen. See attached image. Simply add a new row, tick which Build or Make it should apply to, and select the menu from the Project menu. Quick, Easy and Effective!

Yes.

Now we need some nice ideas how to extend this for:
- search paths (editing paths via typing is error prone)
- depending values. For example: if LCLWidgetSet=win32

Mattias

Reply by email