Indy on windows: staticpackages.inc not found / duplicate identifier INYLAZ

[briantokyo]

I'm unable to install Indy on windows, what's wrong?

http://img21.imageshack.us/img21/8075/tmpe41etmp.jpg

[briantokyo]

Is there no fix for this? Or maybe some other sockets library that works.. ?

[Vincent Snijders]

This error is probably some configuration error, which are hard to fix without seeing you exact configuration.

[clauslack]

I had the same errors..
Follow Indy Install in Windows
http://wiki.lazarus.freepascal.org/Indy_with_Lazarus#How_to_install_.5B3.5D_Windows.2C_Indy_10.2.0.3

Works for me; with some changes.
    *  Need working Lazarus (and FPC) for this (in c:\lazarus)
    * Download from http://www.indyproject.org/Sockets/fpc/index.en.aspx
    * unpack into a directory
    * in the indy /fpc dir
I used make with full path (C:\lazarus\fpc\2.2.4\bin\i386-win32\make.exe)
1. make clean
2. make all
3. make install This will put the indy files into the FPC units directories
(not work, I copy C:\lazarus\components\indy-10.2.0.3\fpc\units\i386-win32 to C:\lazarus\fpc\2.2.4\units\i386-win32\indy)

* From within Lazarus do a Package -> Open package file -> from the indy  /lazarus dir, open the indylaz.lpk
* In the "Compiler options" put
C:\lazarus\fpc\2.2.4\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)

After, in each project, in Compiler options, I put C:\lazarus\components\indy-10.2.0.3\fpc\ in other source for the IDE.

Tested in
- Lazarus 0.9.27 fpc 2.2.4 svn 20212 (26/05/2009) with Windows XP SP3 and Windows 2000 sp4

Regards

[cpalx]

Hello, did you try to copy that file to the main path of indy folder
is indy folder in components folder ?

[Leledumbo]

I've had this before, the true error is in the staticpackages.inc. Sometimes, after editing Package->Configure installed packages when updating a package, the old entry isn't removed. This causes the entry to be doubled. AFAIR, the remedy is to rebuild Lazarus without the package at all then reinstall the package. 1 more, if you've ever got the message like the topic's subject, restart Lazarus first.

PS: Manually editing staticpackages.inc might help if you don't rebuild via Package->Configure installed packages (because this dialog will overwrite any changes you did).