I found the below IOS library a few days back now and I am going to try and build an IOS External using it so I can finally (and hopefully easily) have the ability
to embed a FTP Server into a LiveCode IOS Application.

Reading through the documentation in the download it has a comprehensive how-to in terms of adding the libpureftpd.a file to the Xcode Project and the other dependencies but when I run a build I am getting the following error..

"linking step of external dylib build failed, probably due to missing framework or library references - check the contents of the iosftpserver.ios file"

I believe it is telling me that I haven't defined the framework for the library in the .ios file but how do I find out what framework the library requires?

on myTrigger
myHandler
end myTrigger
on myHandler
answer "foo"
end myHandler

then call myTrigger...
which leads to a single call to the myHandler bit and all is Ok

Unless the compiler is really clever and can read minds (or some such) it would not really know that you are trying to call a 'different' function called 'pureftpd_start' from within your function 'pureftpd_start'. Therefore it'll get confused. It's basically a recursive function call - which is not what you want here.

So, the two stage approach would work ok as long as the names are not the same

Hope that helps a bit more,

Dave

Coding in the Sun - So much Fun.
Visit http://electronic-apps.info for released App information.

As the .lcidl file can complete tasks on startup and shutdown (according to the LC Youtube video) I think I may just try placing something like below in the .lcidl file as you suggest.
What are the thoughts on trying this?

In general you would need to '#include' the headers for the pureftpd stuff, make sure that the files (.c/.cpp/.mm/etc) are in the right places so that the compiler can see them and add them to the make process and then make sure that the compiler knows to link to the created library file.

The use of main was just an example. main() is the starting point for virtually all 'C' programs (think of it as the openStack handler for the mainStack in LC ). I don't know of any programs that will work without a 'main' (in my limited experience - I'm sure that there are though!), so I used it as an example only.

At this point in time I haven't actually made any externals for LC so I cannot talk from a state of knowledge - Monte would be better at that. But in general I would suggest getting the hang of some more of the basics of C-Programming before heading into the complicated world of external making. I'm not suggesting a few years of meditation and knowledge absorbing - just get the standard understanding of 'hello world' and how the compiler/linker works. After that it will become a lot easier for most projects - hopefully!