Why are bridges in the general build
On Sat, May 5, 2012 at 11:05 AM, Leslie Spiro <email@example.com> wrote:
You can configure with --without-middleware-bridge and no bridge will be
built. Likewise you can specify --without-payload-bridge to build
without a payload
I definitely like the idea of a NULL bridge for testing and as a
documented template for writing
I am not sure that separate bridge builds make sense. When I download
source, I expect to run
configure, make, make install and build something useful. I prefer to
make the configure scripts
smart enough to build build painlessly. One option is for the default
automatically build bridges if all the required packages (middleware,
tools, etc.) are found in
the default locations. Updating configure.ac can be painful, but you
usually only have to do
Currently, I think we need to make the avis configuration more sophisticated.
Also as the number of bridges increase we don't want to keep changing the
Leslie Spiro <lspiro@...>
Reading the difficulties that William is having getting the Avis bridge to build, wouldn't it make sense to split the build into open mama core (possibly including a null bridge as an example for bridge and payload writers), and then have separate bridge builds ?
Also as the number of bridges increase we don't want to keep changing the build as each new bridge is released.
I can build all of the projects under OpenMAMA 2.1 solution (Windows 7, VS 2010).toggle quoted messageShow quoted text
1. flex - http://gnuwin32.sourceforge.net/packages/flex.htm
2. avis-client - http://avis.sourceforge.net/downloads.html
1. add AVIS_HOME variable with path to avis-client as value.
2. append path to flex executable to system "Path" variable
Fix paths in solution:
1. for all of the projects which depends on avis-client lib, remove Debug after AVIS_HOME.
On 5.05.2012 21:05, Leslie Spiro wrote: