Menu

Tree [r103] /
 History

HTTPS access


File Date Author Commit
 3rdparty 2011-06-24 singe-de-code [r101] Test tools, tweaks to spell-checker threading, ...
 build 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...
 ide 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...
 include 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...
 src 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...
 tests 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...
 text_to_speech 2011-03-28 orthomaker [r77] Test new svn client
 tools 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...
 BUILD_ALL 2011-04-07 singe-de-code [r83] Further refactoring, diagnostics, ...
 README 2010-11-19 singe-de-code [r11] Add basic README
 _DESC.TXT 2011-07-20 singe-de-code [r102] test and doxygen updates, etc.
 _TASKS.TXT 2011-06-24 singe-de-code [r101] Test tools, tweaks to spell-checker threading, ...
 coregraf.dox 2011-07-20 singe-de-code [r102] test and doxygen updates, etc.
 coregraf.workspace 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...
 coregraf_deprecated.workspace 2011-09-03 singe-de-code [r103] build updates and code changes to quieten gcc w...

Read Me

COREGRAF README

README               this file

BuildMe              shell script to build all modules with make
coregraf.workspace   CodeLite workspace

coregraf_old         CoreGraf core
conjugengine         prototype conjugation engine (ongoing)
test_harness         test harness for coregraf

documentation        Doxygen generated documention
old                  misc old source
orthoengine          old folder

COREGRAF BUILD

The existing, prototype Coregraf modules require only a minimal build
environment at the moment: the  i.e. g++ compiler and standard 
libraries. Additional dependencies will be added here when identified.

The checked-in make files will build with these tools. A shell script
can be found in the root directory, or you can buld the 
individule modules using make.

I have also checked in the CodeLite project files, For prototyping I
am currently using CodeLite IDE, after reading about its GDB 
integration (which I have found very helpful).

LINUX

For prototyping, I am using g++ 4.4 on Ubuntu.

If you already use g++ on you sysem, you should already have all the
components required to build the prototype code. The only possible
exception might be regex.

On Ubuntu, the build essential package should be all thats required:
http://packages.ubuntu.com/lucid/build-essential

Either use a tool like Synaptic Package manager to get the
"build-essential" package, or (for Ubuntu) use the following command
line:

sudo apt-get install build-essential

I am new to Linux, but believe that the same kind of approach should
work for Debian; I am less sure of other flavours Linux. Please let
us know if you hit any problems.

The project is in the process of finalising its toolset, but if you
want to use CodeLite, this can be obtained in a similar way. There
are also i386 and x86_64 install packages for ubuntu 10.4 (lucid),
fedora 12 and 13, and openSUSE 11.2 and 11.3

WINDOWS

To build on Windows, I am using g++ with MinGW-4.4

If you already have a MinGW build environment, you should already have
all the required files. The one I am not sure about is regex; this was
already present on my computer but might have been installed separately.
If you do need additional MinGW files, these can be downloaded from:
http://www.mingw.org/

You can obtain the MinGW toolset from http://www.mingw.org/

See their Installation instructions for details:
http://www.mingw.org/wiki/InstallationHOWTOforMinGW

If you are new to MinGW, or just lazy (like me), you can download a
Windows installer from http://codelite.org/LiteEditor/Download which
installs not only CodeLite but MinGW and GDB.

RUNNING COREGRAF

To run the prototype modules:

1. if you built the module using make, the application can launched
   once built.

2. if you built the module using CodeLite, then the data files'
   subdirectory (./Fichiers) needs to be copied into the Debug or
   Release folder as appropriate.
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.