Re: [lazarus] Naming conventions
Felipe Monteiro de Carvalho wrote: On 7/23/06, Mark Morgan Lloyd <[EMAIL PROTECTED]> wrote: OK, so without having yet investigated your code I presume that this approach tends to put the created binaries in the same place, so the technique is to compile then extract the things to be run before going to the next architecture. I´m not sure what you mean. The binaries are created on the same directory as the source. Binaries from different platforms don´t conflict because usually you will have a copy of the source code on each platform, so the binaries will be located on different partitions or different hard disks. Not always :-) In my case the lazarus sources are located on a nfs share. So building for linux (on a linux box) and building for OSX (on a mac) result in the same exe. (but I don't consider this as a normal situation) Marc _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Naming conventions
Mattias Gaertner wrote: > > sounds like you are talking about "compiling the same source ON > > different platforms" and the OT talks about "compiling the same soure > > FOR different platforms" ;-) Exactly, and depending on how much I get working here that means different CPUs and OSes. > If you mean cross compiling: > You can use makros in output directory names. See all lazarus packages for > example. Thanks for that, will investigate :-) -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Naming conventions
On Mon, 24 Jul 2006 11:58:42 +0200 Burkhard Carstens <[EMAIL PROTECTED]> wrote: > Am Montag, 24. Juli 2006 00:13 schrieb Felipe Monteiro de Carvalho: > > On 7/23/06, Mark Morgan Lloyd <[EMAIL PROTECTED]> wrote: > > > OK, so without having yet investigated your code I presume that > > > this approach tends to put the created binaries in the same place, > > > so the technique is to compile then extract the things to be run > > > before going to the next architecture. > > > > I´m not sure what you mean. > > > > The binaries are created on the same directory as the source. > > Binaries from different platforms don´t conflict because usually you > > will have a copy of the source code on each platform, so the binaries > > will be located on different partitions or different hard disks. > > sounds like you are talking about "compiling the same source ON > different platforms" and the OT talks about "compiling the same soure > FOR different platforms" ;-) If you mean cross compiling: You can use makros in output directory names. See all lazarus packages for example. Mattias _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Naming conventions
Am Montag, 24. Juli 2006 00:13 schrieb Felipe Monteiro de Carvalho: > On 7/23/06, Mark Morgan Lloyd <[EMAIL PROTECTED]> wrote: > > OK, so without having yet investigated your code I presume that > > this approach tends to put the created binaries in the same place, > > so the technique is to compile then extract the things to be run > > before going to the next architecture. > > I´m not sure what you mean. > > The binaries are created on the same directory as the source. > Binaries from different platforms don´t conflict because usually you > will have a copy of the source code on each platform, so the binaries > will be located on different partitions or different hard disks. sounds like you are talking about "compiling the same source ON different platforms" and the OT talks about "compiling the same soure FOR different platforms" ;-) _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Naming conventions
On 7/23/06, Mark Morgan Lloyd <[EMAIL PROTECTED]> wrote: OK, so without having yet investigated your code I presume that this approach tends to put the created binaries in the same place, so the technique is to compile then extract the things to be run before going to the next architecture. I´m not sure what you mean. The binaries are created on the same directory as the source. Binaries from different platforms don´t conflict because usually you will have a copy of the source code on each platform, so the binaries will be located on different partitions or different hard disks. To make things easier, on the magnifier I created a big shell script which I run and select my build options (like build rpm package, build tar.gz package, build freebsd package, etc). This automates the whole process of building a release. -- Felipe Monteiro de Carvalho _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Naming conventions
Thanks both for the thoughts, I'll work on it. > On Lazarus a single project is enougth for any number of platforms. If > you have any platform specific code, just enclose it with IFDEFs and > everything should be fine. OK, so without having yet investigated your code I presume that this approach tends to put the created binaries in the same place, so the technique is to compile then extract the things to be run before going to the next architecture. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Naming conventions
On 7/23/06, Mark Morgan Lloyd <[EMAIL PROTECTED]> wrote: Is there a preferred directory organisation for this sort of thing? I'm assuming that I will end up with distinct forms and user-interface code for Delphi and Lazarus but do I also need to maintain parallel Lazarus projects by target processor and OS? You don´t need distinct user-interface code, only distinct visually designed forms. And with that I mean, a LFM file for lazarus and a DFM file for Delphi. When you change one of them, the other isn´t automatically updated, so this is a problem. On Lazarus a single project is enougth for any number of platforms. If you have any platform specific code, just enclose it with IFDEFs and everything should be fine. One of my projects, the Virtual Magnifying Glass, has visually designed forms, and can be compiled with either Delphi 5 to 7 or Lazarus (at least on Windows, Linux and FreeBSD). It can probably help you understand how to keep the same code compilable with both compilers, and maintain a project like that. You can download the full source code here: http://sourceforge.net/projects/magnifier/ thanks, -- Felipe Monteiro de Carvalho _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Naming conventions
In pricipal all files can live peacefully together in one directory. The pas files are commonly used. Only the DFM and LFM/LRS files are IDE specific. But there is a tool in lazarus that converts DFM into LFM/LRS. You will also need to add some defines though in the pas file to include LResources and some other Lazarus specific units like Buttons. You can use the LCL define or FPC define for that. Darius - Original Message - From: "Mark Morgan Lloyd" <[EMAIL PROTECTED]> To: Sent: Sunday, July 23, 2006 4:19 PM Subject: [lazarus] Naming conventions In order to get myself going properly using Lazarus I intend to take a "simple" file viewing program that I wrote for Delphi 1/3 and port it for Win-32 and Linux. In the latter case I hope to target x86 and SPARC, and might even have a go at Solaris if the v8 I've got is new enough. Is there a preferred directory organisation for this sort of thing? I'm assuming that I will end up with distinct forms and user-interface code for Delphi and Lazarus but do I also need to maintain parallel Lazarus projects by target processor and OS? -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] Naming conventions
In order to get myself going properly using Lazarus I intend to take a "simple" file viewing program that I wrote for Delphi 1/3 and port it for Win-32 and Linux. In the latter case I hope to target x86 and SPARC, and might even have a go at Solaris if the v8 I've got is new enough. Is there a preferred directory organisation for this sort of thing? I'm assuming that I will end up with distinct forms and user-interface code for Delphi and Lazarus but do I also need to maintain parallel Lazarus projects by target processor and OS? -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] _ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
