Source Repository Directory Structure

Written by Score: 1.0 - Comment: Direct, also from friends Clodo , Saturday, April 23, 2011 0:55:50 AM
Directory structure of our SVN repository.
Note that actually (23/04/2011) not all sources are yet released. Look the column "Avail", red items will be released when ready to publish it.

Read also Source Code Overview / Distribution / Deployment for more informations.
PathNotesAvail
clientOsiris Client100%
binBinary files, for each supported platform, architecture, debug or release. Compilation of C++ sources generate and execute binaries here.100%
dataOsiris "data" directory. In debugging C++ sources, Osiris run as "portable" mode, with data here. Read Client Directory Structure for more details.100%
extensionsExtensions developed by Osiris Team. Languages extesions are not here, because generated directly by our Translation System (part of Anubis)100%
138B613D055759C619D5F4EFD9FDB978387E97CBOsiris Core - Required100%
15EC737256997E5993528A94D0540235D59E384BRotator or slide subcontent100%
3A400E99522000141CAC3313A129DF6C57FD9017Osiris Official Portal Extensions. Connect Osiris with Anubis.100%
47987A793879597EC105C43C8E9F25D5ADEB09D8Html2Oml Extended Rules100%
4A7F130B4A5C42CC5D928D157641596A89543C65Osiris Developer Tools100%
5B1D133CA24D2B5B93B675279CB60C9CB7E47502Citation OML Tag100%
9EF66A96C4A73540B8DB46A14D56FF49802ED82FJWPlayer100%
AB0CA5357D587E1E8A2D512DEA15EB0B41788F8EYouTube OML Tag100%
B25720BF660F5C1D273D1CB7E010C11AA85F66CDClocks Flash100%
BE32DBBDE687B9FDFE470AE76A3A91E809400787Alpharis Skin100%
C84236F206B97703C3AA5C4037567D2187D93348Intensedebate Comment System100%
E781E8B0E5F2CFE0FA74CC520756692EE2FB35DDLimpid Skin100%
FBB11DCD3134703D1A2179451C5898B5E3A1DCBBCustom CSS100%
dependenciesC++ headers (.h) and libraries (.lib or .a) of third party libraries. The version used by our compilation projects.100%
objEmpty directories, for each supported platform, where ".obj" files are created.100%
shareThe "share" directory. Refer to the article Client Directory Structure.100%
srcC++ sources and projects.70%
applicationUI Executable100%
consoleConsole Executable100%
firefoxFirefox Extension100%
testappExecutable for testing100%
coreCore library100%
engineEngine library0%
archivesCompressed archives library100%
dbDatabase library100%
httpHTTP library100%
ircIRC library100%
langLanguage/Cultures library100%
netNetworking library100%
sdkSDK Library, for embedding100%
upnpUPNP library100%
webWeb library100%
xmlXML library100%
pluginsPlugins100%
componentsStandard components & modules0%
dhtDHT100%
mysqlMySql Database Layer100%
sqliteSqLite Database Layer100%
pythonPython scripting engine0%
translationsTranslations support / auto-report100%
pluginsampleSample plugin100%
sampleappExecutable for testing100%
testlibLibrary for testing100%
isisIsis project100%
distributeDistribute scripts & output. Isis are not builded or managed by OMS.100%
htdocsPHP source code.100%
htdocs_0XPHP source code of 0.X versions.100%
librariesThird Party Libraries used. Generally RAR compressed.100%
omsOsiris Management System, typically used to build, deploy, and automatic tasks.100%
dataResources used by OMS100%
librariesThird Party binary libraries, for different platform, that are released bundled with Osiris.100%
omsOMS source-code, C# projects.100%
outputEmpty directory, filled by OMS for temporary files.100%
reportsReports generated by OMS, for different platform. For example, for compare different libraries requirement between platforms or architecture.100%
repositoryFinal output directory for packages builded by OMS. Contain also directory-structure for some repository system, as example the support of Debian Aptitude repository.100%
OMS.slnVisual Studio 2005 solution project of OMS.100%
utilsThird Party Software used. We use when possible portable apps for developing, and we commit here the version we are using/testing. Maybe RAR compressed, if too heavy.100%
disk_o.batSimple script that map under windows the drive "O:" to this directory.100%
license.txtGPL License100%

Notes

  • In some directory, may exists a subdirectory called "_work". It's contains resources files that are skipped if the directory is taken by OMS for build a software package.As example, where exists PNG images, the _work directory will contain Adobe Fireworks projects.
  • The same as above occur also with files that start with "xx_".