build errors

[code20]

I have configured the environment variables in setup.cmd:

set MPC_ROOT=Q:\fast\MPC

set XERCESCROOT=Q:\fast\xerces-c-3.1.4

set BOOST_VERSION=boost_1_62_0

set BOOST_ROOT=Q:\fast\boost_1_62_0

however I get the following error when running setup.cmd

>REM Setting up QuickFAST environment
See remarks in setup.cmd for information about setting your build environment
Setup check failed: XERCESCROOT=Q:\fast\xerces-c-3.1.4
Edit the setup.cmd file or change environment variables

given the failures in MPC, how difficult would it be to construct he visual studio project manually?

[Dale Wilson]

On Sat, Nov 26, 2016 at 4:32 PM, code20 <chris...@gmail.com> wrote:

I have configured the environment variables in setup.cmd:

set MPC_ROOT=Q:\fast\MPC

set XERCESCROOT=Q:\fast\xerces-c-3.1.4

set BOOST_VERSION=boost_1_62_0

set BOOST_ROOT=Q:\fast\boost_1_62_0

however I get the following error when running setup.cmd

>REM Setting up QuickFAST environment
See remarks in setup.cmd for information about setting your build environment
Setup check failed: XERCESCROOT=Q:\fast\xerces-c-3.1.4
Edit the setup.cmd file or change environment variables

​

Either you have XERCES_ROOT set incorrectly, or xerces is installed incorrectly, or there is a problem with the check in setup.cmd.  Take a look at setup.cmd to see what it is checking.  This should tell you which of the three cases you have encountered.

​

 

given the failures in MPC, how difficult would it be to construct he visual studio project manually?

​For the record this is not a failure in MPC (which you have not even run yet.). It is a failure in the setup on your machine.  Having a pre-built solution file would not fix this.​

 

QuickFAST is an open source product which runs on a variety of platforms with different build toolchains on the various platforms.    One of the challenges of producing such a project is creating the various files needed to build the project.  Doing it manually is highly labor intensive and error prone.  Every multi-platform project has to address this issue. 

There are several approaches to solving this.  Boost uses BJAM.  Other projects use CMAKE or autobuild.  Most OCI projects (and the ACE/TAO framework) use MPC.   In addition to it being "invented here" we happen to think (with lots of evidence) that MPC is easier to use than the alternatives.

OCI does not generate any revenue from QuickFAST itself or from MPC.   We have made it available as Open Source both as a service to the community; as a way of advertising our skills.  It often leads to consulting engagements and/or sponsored improvements to QuickFAST and other open source projects.      

You ask "how difficult would it be to construct the visual studio projects manually."  Why don't you find out?   You can either invest your time to do it yourself (you have all the source available),  or you invest your money by contacting our sales department (sa...@ociweb.com) to ask us to create a custom build for you. 

Regards,

Dale