I have uploaded all the jam files for the 3rd party libs here:
libjpeg.jam http://pastebin.com/raw.php?i=5v3DgCbS
libpng.jam http://pastebin.com/raw.php?i=BT1Ecd7J
libtiff.jam http://pastebin.com/raw.php?i=480qTSsh
These files should be copied into boost_folder\tools\build\v2\tools
The gil::io Jamfile.v2 is here http://pastebin.com/raw.php?i=6QDjatNd and
it should be put into boost_folder\libs\gil\io\test on the develop branch.
Now ideally the io test suite will built the libs first and then run the
unit tests. But that's easier said than done.
Hope this helps,
Christian
On Wed, May 21, 2014 at 12:57 PM, Harg Tholan
Pass me the details on how can I help you with that. On 16 May 2014 18:41, "Christian Henning"
wrote: Yes, the new io is in the develop branch. One of the reasons it was never fully released is that I just don't have the knowledge and time to get unit test to work. Here I need to be able to compile and link 3rd party libs with boost build and it's painful...
Christian
On Fri, May 16, 2014 at 9:34 AM, William Gallafent
wrote:
On 15 May 2014 12:23, William Gallafent
wrote: It is present in boost's subversion trunk[4].
Following this list indicates that boost has made a transition to git (I know, not paying attention :). I had a look in the git repository[6] … and see that io_new is on the “develop” branch but not “master”.
[6]
https://github.com/boostorg/gil/tree/develop/include/boost/gil/extension/io/...
-- Bill Gallafent.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost