Hi,
I have a question about the best practice for distributing open source code developed in SlickEdit.
We have developed a large project on Linux using SlickEdit (
http://www.jitterbit.com). The project was ported from windows where we use visual studio as our development platform and we are happy with SlickEdit since it gives a similar experience on Linux. Now we are releasing the code as opens source and want to encourage other people to download and compile the code. What would be the best way to convert the SlickEdit projects (we have like 80 of them with complicated dependencies between them) to something that can be compiled without having access to SlickEdit, since SE is not that common in the open source community.
I understand that SlickEdit can generate Makefiles, but will these Makefiles keep track of the dependencies between modules, compile files in the correct order etc etc.
Any suggestions are welcome.
/Thanks
Emanuel
Emanuel Norrbin
Software Engineer, Jitterbit Inc.
http://www.jitterbit.com/
