Dear all,
when I put a csvexporter on a form lazarus automatically adds to my project lazdbexport unit if I am under windows and fpccsvexport if I am under Linux.
So I have to do this:

  {$IFDEF WINDOWS}
  lazdbexport;
  {$ENDIF}
  {$IFDEF UNIX}
  fpcsvexport;
  {$ENDIF}

Is it ok?
Andrea

An embedded and charset-unspecified text was scrubbed... Name: not available
Url: http://www.lazarus.freepascal.org/pipermail/lazarus/attachments/20081216/1d8a6c41/attachment.pl

I am developing a cross platform application.
Yesterday I dropped a csvexporter on a form (and I was under win). The lazdbexport unit have been added by the IDE.
Then today, working on my Ubuntu pc at home I tried to recompile the same project and I got an error (lazdbexport unit not found), so I opened an empty project and I dropped csvexporter on the form. The IDE added the fpccsvexport unit, so I introduced the IFDEFs. I supposed that the IFDEF were in the package.
Anyway I used the csvexporter just a bit and it seems to work fine both on win and linux :).
Regards,
Andrea

Mattias G?rtner ha scritto:

There are none ? There is no OS-dependent code in the exporters.

Anyway I used the csvexporter just a bit and it seems to work fine both on win and linux :).

This is strange, because the unit is called "fpcsvexport.pp" ?

Michael.

Do you use the same lazarus/fpc versions on both windows and linux?

Vincent

Michael Van Canneyt ha scritto:

I didn't explore the source code of the exporters, sorry.

Yes, fpc 2.2.2 and lazarus svn
andrea

Vincent Snijders ha scritto:

Dear all,
I have to correct my thread. I checked again both on win and on linux. Both under win and linux when I put a csvexporter on a form Lazarus adds lazdbexport unit in the uses clause of the project (lpr) and fpcsvexport in the uses clause of the form unit.
I misunderstood the lazarus behaviour because Lazarus failed to compile my project under linux saying that "Lazarus can't find unit lazdbexport used by...".
Now I added a new csvexporter to my form, I compiled my project and deleted the new csvexporter and compiled again, and it works. I am not able to understand exactly what is the problem I suppose it is related to something in the lpi file.
I am sorry for my mistake.
Andrea

Andrea Mauri ha scritto: