Archive

Archive for July, 2009

Starting development in C++

July 9th, 2009

Not having a single line of code in this project in C++, and having successfully compiled the C++ projects, makes me an ideal commentor for “How to Start Development in C++”.

These are the stages you will have to follow.

  1. First, take a look at this previous post. .
  2. Obtain the code from the repository.
  3. Install a Visual C++ 2008 compiler. If you cannot pay the license, you can download the “Visual C++ 2008 Express” edition. It is free and it has everything you may need to start working.
  4. Install “log4cxx” and compile it. It is the equivalent of log4j in c++. You may be a hero, and correct the several bug this version has (unconceivable, but it is so). Or you may trust others heros who did it. The resulting log4cxx.dll file should be available in the PATH. Don´t forget making available the .lib files to the linker.
  5. Install “codexynthesis XSD“. It generates C++ wrappers from XSD schemas, much like JAXB does. It includes Xerces for C++, whose .lib should be available for the MXM projects. The XSD executable, should be available in the PATH also.
  6. Open the MXM projects from Visual Studio and compile. If you adore black screens, you can also install ant (or even worse, maven). But before, you should make Visual Studio binaries in the path, running VCVARS32.bat (available in the bin folder of Visual Studio).
  7. If you use Visual Studio, you will have to update all the directories (folders for includes, etc.) to your computer´s configuration.
  8. Voila! It should compile.
  9. To test the metadata engine, there is a .EXE application which needs three parameters to be run (log4cxx.properties, MXMConfiguration.xml properties and metadata.xml itself)…. You should create an adequate log4cxx.properties file, and you should change the parameters in the MXMConfiguration.xml to your choice (for example, change the folders etc.)
  10. Good luck!

victor News

C++ source code available

July 6th, 2009

A first release of the C++ source code for the modules mxm-coremxm-dataobject, basic-metadata-engine and metadata_mxm_test have been committed today on the MXM svn repository.

The committed source code can be retrieved with an svn-update and it’s located in
http://wg11.sc29.org/mxmsvn/repos/C/src/

The project files for win32 (visual studio 9.0) are located in
http://wg11.sc29.org/mxmsvn/repos/C/win32/

The project files for linux (g++) are located in
http://wg11.sc29.org/mxmsvn/repos/C/linux/

With the mxm_core you can enjoy loading and managing the different MXM engines in a common enviroment. The mxm_dataobject can be used to wrap a generic MXM schema in a set of C++ classes. The basic_metadata_engine is a very simple implementation of the MXM MetadataEngine (it retrieves the mpeg-7 title of a mpeg-7 document) and can be used as an example on how to create a MXM engine. Finally, the metadata_mxm_test is deployed to test the basic_metadata_engine.

Any information regarding the MXM C++ source code can be found here: http://mxm.wg11.sc29.org/?page_id=60

Enjoy the MXM C++ code :)

angelo News

MXM adopts BSD License for its Reference Software

July 3rd, 2009

The copyright in this software is being made available under the BSD License, included below. This software may be subject to other third party and contributor rights, including patent rights, and no such rights are granted under this license.

<OWNER> = Regents of the University of California

<ORGANIZATION> = University of California, Berkeley

<YEAR> = 1998

Copyright (c) <YEAR>, <OWNER>

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Neither the name of the <ORGANIZATION> nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Christian Timmerer News , ,

-->