Difference between revisions of "Indy with Lazarus/es"

From Lazarus wiki
Jump to navigationJump to search
Line 63: Line 63:
 
* During demo conversion, the bindings property is often wrongly converted. This can result in strange errors, specially because Indy seems to bind to the same port using both IPV4 and IPV6 from time to time. Not fully debugged yet.
 
* During demo conversion, the bindings property is often wrongly converted. This can result in strange errors, specially because Indy seems to bind to the same port using both IPV4 and IPV6 from time to time. Not fully debugged yet.
  
−
=== How to install ===
+
=== Como instalar ===
−
[[user:Matthijs|Matthijs]]: So it is not perfect yet, but you want to try it. Here is how you install it in Lazarus.
+
[[user:Matthijs|Matthijs]]: Por lo que no es perfecto todavía, pero puedes probarlo. Here is how you install it in Lazarus.
−
* Open and compile indysystemlaz.lpk
+
* Abre y compila indysystemlaz.lpk
−
* Open and compile indycorelaz.lpk
+
* Abre y compila indycorelaz.lpk
−
* Open and compile indyprotocolslaz.lpk
+
* Abre y compila indyprotocolslaz.lpk
−
* Open, compile and install dclindycorelaz.lpk
+
* Abre, compila e instala dclindycorelaz.lpk
−
* Open, compile and install dclindyprotocolslaz.lpk
+
* Abre, compila e instaladclindyprotocolslaz.lpk
−
Then rebuild Lazarus and you will see a 15 tab's with Indy components.
+
 
 +
A continuación reconstruye Lazarus y verás 15 solapas con componentes Indy.
  
 
=== How to install on debian/ubuntu ===
 
=== How to install on debian/ubuntu ===

Revision as of 00:28, 8 July 2009

│ Deutsch (de) │ English (en) │ español (es) │ français (fr) │ 日本語 (ja) │ 한국어 (ko) │

Indy for Lazarus

El equipo del núcleo de Indy está realizando un nuevo intento de conversión para su funcionamiento con FPC/Lazarus. El desarrollador de FPC Marco van de Voort está trabajando con el núcleo de Indy para que funcione completamente con FPC/Lazarus. Indy's JP Mugaas realizó un gran trabajo para tener Indy10 trabajando con FPC. También el backend nativo unixrtl backend es en su mayor parte trabajo suyo.

Actualmente Indy10 está casi trabajando con funcionalidad completa, y la funcionalidad para el usuario final se ha mejorado mucho. Solamente algunos temas como OPENSSL y la compresión necesitan conocimientos adicionales. El soporte para 64 bits tampoco se ha validado completamente todavía.

Sugerencia: No estoy demasiado interesado en el soporte de la versión para Kylix de Indy.. (cualquier cosa que utilice la unit libc). Unicamente la porté como un paso hacia una RTL nativa de Unix utilizando aplicaciones con Indy.

Requerimientos

Currently, FPC 2.0.4 is very close to being able to use indy in all its facets, except for the server bug on FreeBSD/Mac OS X (which requires 2.1.1)

Since Indy10 now works for all major targets, we focus on this version. While conversion to Indy9 might be simpler for people, keep in mind that it only works on win32. (and theoretically could be ported to Linux/x86).

Therefore we recommend people to work with 10 as much as possible.

(For indy9, you might need to remove the overriding of tmemorystream.setsize method (Marcov: ???) to get telnet components working, but Indy9 hasn't been tested in a while)

The port is fairly stable, and JP Mugaas has done a great deal to improve the quality of the release, a set of makefiles inclusive

Downloads / Links

Current snapshots (for die hards only) are at

What works, what not

Indy9:

  • Windows should largely work. Lots of demoes ported.
  • Linux not or barely. No hope at non Linux/x86 (non-Kylix) targets.

Indy10: (Indy10ForFPC branch)

  • Windows and Unix: clients work and servers should work fine in principle.
  • The main work for native Unix RTL done. Servers Clients seem to work with FreeBSD and OS X

All: secure versions not tested yet.

Short term plans

  • Convert demoes to demonstrate/test workings.
  • Fix bugs and enter them back into FPC or Indy RCS.

Problems

  • Indy9 and Indy10 are mutually exclusive, which causes problems for deployment, even the default is a problem:
    • Indy9 is more used and proven in the industry.
    • Indy10 is more portable, and better long term. However uptake seems to be low, and there is not much movement at Indy anymore.
  • How to deploy? Parts belong to Lazarus, parts to FPC.
  • Lot of pkgs and demoes have paths in them. How to centrally fix them so that unexperienced users can build them?
  • Lazarus problems
    • Transparancy problems of icons
    • component tabs don't scroll, if you put a lot of components in one tab, they are not selectable. workaround implemented: JP Mugaas separated them into Indy clients A-M and N-Z etc. Also, meanwhile Lazarus changed to two rows of components per tab.
  • Indy demoes (specially Indy10's) are not very suitable for multiplatform usage. Their setup is awfully windows specific, with spaces in paths, deep nested dirs, and useless baggage (C# code). A short working set of demoes will have to be created.

Bugs

  • Indy10 servers didn't work before due to an exception occuring during startup, which shut everything down. You need FPC 2.2(.0) or later to fix this (pthread_kill problem). This probably also affects Mac OS X.
  • During demo conversion, the bindings property is often wrongly converted. This can result in strange errors, specially because Indy seems to bind to the same port using both IPV4 and IPV6 from time to time. Not fully debugged yet.

Como instalar

Matthijs: Por lo que no es perfecto todavía, pero puedes probarlo. Here is how you install it in Lazarus.

  • Abre y compila indysystemlaz.lpk
  • Abre y compila indycorelaz.lpk
  • Abre y compila indyprotocolslaz.lpk
  • Abre, compila e instala dclindycorelaz.lpk
  • Abre, compila e instaladclindyprotocolslaz.lpk

A continuación reconstruye Lazarus y verás 15 solapas con componentes Indy.

How to install on debian/ubuntu

  • # cd indy-10.2.0.1/fpc
  • # chmod +x debian/rules
  • # touch README
  • # sudo apt-get install fakeroot
  • # dpkg-buildpackage -rfakeroot -uc
  • # cd ..
  • # sudo dpkg -i *.deb
  • install package indylaz.lpk in lazarus

How to install [2]

If you couldn't install Indy for Lazarus with tips above, you can try this...

From Yahoo! Brazil, Lazarus Group (User Everaldo)

Version installed on Lazarus 0.9.24 using component indy-10.2.0.1.

  • Unzip the component from file tar.gz (must be this file, the "zip file" does not work) in directory $(LazarusDir)\components;
  • Go to directory $(LazarusDir)\components\indy-10.2.0.1\ and to create inside them a directory named "saved";
  • Copy the content of the directory $(LazarusDir)\components\indy-10.2.0.1\lazarus\ to directory "saved" created above;
  • Copy the content of directory $(LazarusDir)\components\indy-10.2.0.1\fpc\ to directory $(LazarusDir)\components\indy-10.2.0.1\lazarus, and rewrite all files, ok;
  • Get the content of directory "saved" and copy inside of $(LazarusDir)\components\indy-10.2.0.1\lazarus and you can delete "saved" directory now;
  • Install the package laz.lpk (available in $(LazarusDir)\components\indy-10.2.0.1\lazarus\indy) of conventional way.

On LINUX the path is: /usr/lib/lazarus/components/indy-10.2.0.1/, right!!!

I hope this was helpful for you, good luck!!!

How to install [3] Windows, Indy 10.2.0.3

1. make clean 2. make all 3. make install This will put the indy files into the FPC units directories

  • From within Lazarus do a Package -> Open package file -> from the indy /lazarus dir, open the indylaz.lpk
  • In the "Compiler options" put

c:\pp\units\i386-win32\indy\ (or wherever the FPC indy units are installed after "make install") into the "Other unit files" field

  • compile then install (will rebuild Lazarus)
Retrieved from "http://wiki.freepascal.org/index.php?title=Indy_with_Lazarus/es&oldid=36551"