Re: [Doxygen-develop] Morirz First Releas on sourceforge.net
Brought to you by:
dimitri
From: <Eck...@t-...> - 2006-05-31 16:25:50
|
Dear Mr Dodge. Sorry but I'm a newbe in opensource and sourcefaorge. The moritz-unix doesn't mean that this is a unix-project. Sourceforge asked for an unique unix-name for the project. I didn't really understand what they want and I took the prefix unix because I don't use this in any other keyword of the project. Today I know it was a big failure of mine and I will ask if this can be changed. To build Moritz just the following files has to be used: src\ diverse\ c\ KeyListSet.cpp MoritzHelp.cpp String_imp.cpp h\ KeyListSet.h MoritzHelp.h String_imp.h Moritz\ c\ main.cpp xmlblock\ c\ xmlBlock.cpp h\ xmlBlock.h xmlvisitor\ c\ tool_gennsd.cpp tool_nsdanl.cpp xmlVisitor.cpp xmlvst_fileanl.cpp xmlvst_fncbdy.cpp xmlvst_fnchd.cpp xmlvst_gennsd.cpp h\ tool_gennsd.cpp tool_nsdanl.cpp xmlVisitor.cpp xmlvst_fileanl.cpp xmlvst_fncbdy.cpp xmlvst_fnchd.cpp xmlvst_gennsd.cpp Don't use the other sources especially those in the wx-directories. This files are necessary for the wizard I want to write in the next time. (Sorry for the confusion they corse) This are the standard include-files of c/c++ used by Moritz: map.h set.h vector.h list.h fstream.h string.h sstream.h sys/stat.h Since Moritz is a common console-application no special libraries are necessary. I'm not very familiar with make-files and use an ide (DevC++, Code-Blocks, MinGW Developer-Studio, ...) to manage the project and the compile-process. I don't use special compiler-options to optimize the program. For me the only steps to compile the sources is to add them into the ide-project, add the 3 h-paths and start the compilation. I hope this will help you. Dave Dodge schrieb: > On Tue, May 30, 2006 at 10:05:55PM +0200, Eck...@t-... wrote: > >> You can download it under : "www.sourceforge.net/projects/moritz-unix" >> > > Is this supposed to be usable on Unix systems yet? It's a little > confusing because the project name is "moritz-unix" but all of the > released files are listed as "win32". For example I took a quick look > at the source files and didn't see any Makefiles or build instructions > anywhere. > > -Dave Dodge > > > |