...
1. Remove all previous indy installation
2. Download the following package(10.6.2.5274) from: http://www.2shared.com/file/eCHHk96r/Indy_1062.html
3. Extract the zip to $(LazarusDir)/Components/ directory
4. Open the package file, compile twice
5. Install Indy
6. Create a new project, add a few indy components(IdFTP for example) then go to Project/Options, add indy directory to Search Paths(http://i1269.photobucket.com/albums/jj581/balazsszekely/Indy%2010_1_zpsq0ydkwxb.png)
7. Build then Run (http://i1269.photobucket.com/albums/jj581/balazsszekely/Indy%2010_2_zpszknc3fwb.png)
Just for my own information (as I don't have any access to a Mac neither)...
1/ You are adding the Indy binaries path to your project (step 7). Is it really necessary ? Is it a specific need for the OSX ? Is it also the case if you add manually (i.e. when not using a "visual" Indy component) the Indy package into the required package list ?
I mean, theoretically when using a "visual" component, indylaz is added automatically in the required package list, and the path to the Indy binaries are also added automatically when the compilation is done.
And for the other case, adding the Indy package into the required package list should be sufficient (this is the way to provide compatibility between various installations for a package; the exact location of the package binaries may be different from a user/computer to another).
Is all this mechanism not working properly for OSX ?
2/ I see you've chosen the "all in one directory" option for installing Indy. Is it just because you are used to do it (I know it was necessary in the past, unless modifying the lazarus package file) ? Or is it because the "subdirectory" option is not working when installing Indy on OSX ?
I mean, the Lazarus package file released currently with Indy is supposed to now work properly with subdirectories; at least, it's the case with Windows.
Is it not working with OSX ?