I have been using Indy a lot in Delphi so when now looking at what can be done with FPC/Lazarus I am interested in the way Indy can be used.

I found the Wiki page:
http://wiki.lazarus.freepascal.org/Indy_with_Lazarus from which I came to the Indy page:
http://www.indyproject.org/Sockets/fpc/index.en.aspx Here it is stated that the latest version is indy-10.2.0.3 from Nov 2007!

Can this really be true? Is there no later version available? Or maybe the Indy-for-FPC has died?

Le 25/10/2010 20:11, Bo Berglund a ?crit :

Here is an excerpt of Atozed newsgroup (no web mirror) :

------------------------------------------------------------- "Koriolan" wrote in message
news:...

> Where is the Indy 9 for freepascal/lazarus ?

There isn't one. Indy 9 never supported FPC.

> The Indy 9 for freepascal is > http://www.indyproject.org/Sockets/fpc/index.en.aspx

That is for Indy 10, not Indy 9. That is an old page anyway. Support for FPC was merged into the main Indy 10 codebase a long time ago. Follow the links on the main Indy website to the Indy 10 (Tiburon branch) code, and compile the FPC packages in it.

-- Remy Lebeau (TeamB)

---------------------------------------
Le 08/09/2010 11:43, thierrybo a ?crit :

Sorry, I just saw the note on
http://www.indyproject.org/Sockets/Download/svn.EN.aspx :

Note: The "trunk" folder in the Indy 10 repository has an old version.

The "Tiburon" branch contain the current version for now. This will be resolved in a later version when Indy 10's Unicode functionality has been completed.
------------------------------------------
"thierrybo" wrote in message
news:...

> Sorry, I just saw the note on > http://www.indyproject.org/Sockets/Download/svn.EN.aspx :

That note is outdated. The trunk was recently updated, but the website has not been updated yet.

-- Remy Lebeau (TeamB)

-------------------------------
"thierrybo" wrote in message
news:...

> Is https://svn.atozed.com:444/svn/Indy10/branches/Tiburon folder the > only choice ? I saw some FPC code in > https://svn.atozed.com:444/svn/Indy10/trunk folder also. What are the > differences between them ?

The trunk was recently updated to contain the Tiburon code that shipped with
Embarcadero's new RAD Studio XE release. The code in the Tiburon branch contains newer code that is not in the Trunk yet.

-- Remy Lebeau (TeamB)

Le 25/10/2010 23:01, Thierry B. a ?crit :

If I use latest sources from Tiburon branch (Indy 10.5.8+) I can install Lazarus package in lazarus Win 32 (did not succeeded on Linux):

http://a.yfrog.com/img130/5787/screenshot004lh.png

However it seems FPC support is the main goal, all paths to units are not correct in /Lib/indylaz.lpk. If you remove units and insert them again one by one it works. I attach modified indylaz.lpk to the mail but I think it will be blocked.

However I did no test if you can *really* use this version.

Thierry B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: indylaz.lpk.zip
Type: application/zip
Size: 1762 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20101025/c1f0d612/attachment.zip>

Thierry B. wrote

> > Where is the Indy 9 for freepascal/lazarus ? There isn't one. Indy 9 never supported FPC.

This is wrong. There is a port that did support Windows. I never bothered with Linux (because the libc using Kylix port was on the way out anyway)

But its use is not recommended and a dead end.

Recently the Tiburon branch has been merged back to trunk.

Indy is also planning to abandon the system/core/protocols package distinction.

Afaik indy10 works with Lazarus runtime, but afaik the designtime support hasn't been updated in a while.

Yes, I saw that on the Embarcadero newsgroups.

I am mostly interested in Lazarus for cross-platform use so if it is only possible to use Indy10 with Lazarus/fpc on Windows then I am out of luck here... :-(

Initially I want to program on Windows (because this is what I am most used to) but to program/compile on Ubuntu Linux on X86 will be the next step. And finally cross-compiling for embedded Debian Linux for ARM.
So whatever I choose must work on all these targets. Although I do not plan on actually running Lazarus on the embedded platform, I hope I can cross-compile for it...

I am not planning to use many Indy functions though, mainly the standard TCP server and client plus FTP and possibly SMTP client for sending emails.

Bo Berglund

2010/10/26 Bo Berglund

Please read Marco message carefully, I read it as: Indy 9 is for windows only
Indy 10 is cross platform.

Vincent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20101026/718002ee/attachment.html>

Which is correct.

Good to know! :-)
I'll continue along these lines then.

BTW: Is there a way to get the Indy10 files in Linux format? There are different line endings in Linux than what is in the Fulgan zip file which is Windows line endings, I believe). I assume that you have to have Linux line endings in order to make it work with Lazarus on Ubuntu?

Bo Berglund

Le 26/10/2010 14:43, Vincent Snijders a ?crit :

Yes, I was speaking about Lazarus package only...

Lazarus can work with both line endings on all platforms (as well as the compiler by the way). The only thing you can't is mixing the line endings in one file as Lazarus will use the line ending of the first line (but the compiler will accept those files ^^).

Regards,
Sven

Very good!
I have had bad experience earlier with files on Linux/Solaris being edited via samba shares from windows and then the functions controlled by these files stopped working because of the Windows line endings.... So now I can proceed to unpack the zip file from Windows via the samba share to Ubuntu and then inside Ubuntu use these transparently, right?

Or maybe better yet: I import the Indy files into my CVS server on Windows and then I check them back out in Ubuntu, thus making CVS fix the line endings....

Will the Lazarus source editor keep the file line endings if I edit a file in Ubuntu that was originally moved there from Windows and thus has the CRLF line endings?
So that if I add new lines they will retains the original line endings when I save?

Bo Berglund

yes

Or maybe better yet: I import the Indy files into my CVS server on Windows and then I check them back out in Ubuntu, thus making CVS fix the line endings....

yes, even better

As far as I remember this was implemented in 0.9.29, so you need a 0.9.29.

Keep in mind that a samba share is a case insensitive file system, while the compiler and the IDE under Linux work case sensitive. Maybe you want to rename all files lowercase.

Mattias

Mattias Gaertner wrote

Keep in mind that a samba share is a case insensitive file system, while the compiler and the IDE under Linux work case sensitive. Maybe you want to rename all files lowercase.

Not really a good idea because inside the Indy files are uses statemants like this example:

uses
Classes,
IdGlobal,
IdRawBase,
IdRawClient,
IdStackConsts,

  IdBaseComponent;

As you can see these are capitalized and if the corresponding file name is lower case only then it will not be found...

Bo Berglund

No, this is wrong.

FPC searches for
1) the unit as written in the "uses"
2) the unit in all lowercase
3) the unit in all uppercase

(see here at the lower half:
http://www.freepascal.org/docs-html/user/usersu7.html#x21-280003.1.2 )

So the unit will be found if its file is named in lower case.

Note: The casing of "unit UnitName;" inside the file doesn't matter (it doesn't have to match the filename in casing), but it is used by Lazarus when autocompleting a unitname in the uses-clause.

Regards,
Sven