Hi Tommi, thanks for fixing so fast!
Am 26.03.2012 19:49, schrieb Tommi Mäkitalo: > [..] true - this is just wrong. Some times ago I fiddled a little with > shared libraries and broke the generated makefile. I fixed it in svn now. :-) > I am thinking, if this tntnet-config is the best way to start with a > tntnet project. It generates a very simple test project. But it is so > simple that it is just good enough to try out or demonstrate tntnet > but there should be a way to generated a better project. Some times > ago I added the option "tntnet-config --autoproject" to generate a > autotools based project. Yes. I used that. But is very complex for the first time. > But it is not that flexible. And I just realized, that it is neither > mentioned in the help page of tntnet-config nor in the man page. Thats right, but now past. ;-) > In the long term it would be great, if we can create some kind of > plugin in e.g. KDevlop or some other IDE, Vim ? :-D Evtl. Eclipse could be interesting. > where it is easier not only to generate a project but also maintain > it. Frequently you need to add ecpp-pages, cpp code or libraries to > your project. Also automatic generation of dependencies is really needed. If i understand right, it shouldnt be a great problem adding files and Im not sure, doing that automatically ist the right way. evtl. in a IDE like KDevelop or vim this seems senseful. Is it a great thing taking all files in the webapp/-dir ending .h or .[e]cpp for compiling automatically? This should be enough imho. Maybe, for vim, i can do a bit coding if i know what functionality you want. Regards, Oliver ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
