Has anyone tried to compile this under windows?
I will likely try building it under Linux (Latest Ubuntu) via a VM but I have Win 8.1 on my development machines.
I figured out how to get Cmake to work on my machines and will likely use VS 2010 or 2012 to compile unless there is a more compatible C++ compiler. I am assuming under linux you are using GCC which is also available for windows as well.
There are 4 external libraries listed as requirements and I assume those will be needed for my windows build as well. The libraries I mention are libltdl (libtool), libjson-c, and boost from the readme file.
Anyhow this is not a high priority project for me but I would like to try getting it to compile under windows in the next month if possible. I would like to see if it will run under windows with little modification.
Beyond that I am assuming there is a way to tell cmake what OS it is being built for so it will incorporate files based on the OS it is built on? And if so how will that affect any project AMB is involved with such as TIZEN?
Will I need to build an equal but separate fork or will I be able to build the Windows compatibility right in?
Asking before I get too involved in this...
Thanks for your time! If I can get it working it will save me lots of time down the road.
In a release early and often fashion, 0.13 has been released just 2 months
and 4 days after releasing the 0.12 final release and just 6 days after the
There have been 3 major focuses for this version:
1 - Support for the W3C automotive business group vehicle and data specs
2 - Documentation improvements
3 - Tool improvements.
AMB support for the W3C auto-bg vehicle and data specs started in 0.12.
0.13 has additional API support: set(), availability() as well as data
type support for the data spec. Another related change is that the
crosswalk plugin has moved into the AMB source tree (see xwalk/).
I hope to do a blog sometime in the future about testing and developing
with the vehicle web API. Stay tuned!
Documentation has also greatly improved. We've added bluemonkey docs,
documented the websocket protocol, and enhanced the library and DBus
documentation. Check out the new docs here:
AMB 0.13 adds a new tool for amb testing and development: ambctl. This
tool replaces amb-get, amb-set, amb-listen, and amb-get-history.
Blog about this new tool here:
For a more comprehensive list of AMB changes, check out the release notes:
0.14 already has some pretty cool features: more ambctl and documentation
improvements, better plugin handling (plugins.d support), xwalk vehicle
extension now supports all data that AMB does, and new DBus export
 - Support for all non-controversial data elements. What is supported
is documented in the AMB DBus docs.
I've just submitted a pull request that I hope will become AMB 0.13 final.
Please review, test and let me know if you run into any problems.
One of the big improvements in 0.13 has been the documentation. To build
and view the docs, run:
cmake .. -Denable_docs=ON
sudo make install
You will need doxygen and dot to generate the documents.
After you have installed the documentation, you should be able to navigate
to /usr/share/doc/packages/automotive-message-broker/html/index.html and
see all the documentation about plugins, protocols, APIs, etc.
I will probably make a few more pushes to the pull request during the 5 day
review window if I find any more fixes.
0.12.2 is a bug fix version on top of 0.12. Fixes include a fix for a
segfault when calling org.automotive.Manager.List() with no supported
properties, and a fix for the gps nmea plugin on 64bit.
To get this latest version, checkout the 0.12 branch on git:
git clone https://github.com/otcshare/automotive-message-broker.git
git checkout -b 0.12 origin/0.12
"Hacky" new year,