Re: [boost] [gil] External header files.
On 1 March 2010 18:54, Enrique Nieloud <enieloud@gertrudisgraphics.com> wrote:
I just wanted to report that the following two links are broken:
boost/gil/extension/numeric/sampler.hpp boost/gil/extension/numeric/resample.hpp
In the file: http://www.boost.org/doc/libs/1_42_0/libs/gil/example/resize.cpp
That's a pain. The html file is generated automatically from the source file, which states that it's including files that don't come with boost. It'd be better if they weren't expected to be in the boost file system. Daniel
Hi, It would be a great thing to have a repository with all proposed gil extensions, and not only some zip files on adobe site. It would be a great thing to use global includes to boost gil in all extensions, like : #include <boost/gil/gil_all.hpp> and no : #include "../../boost/gil/gil_all.hpp" which imposes to copy this extensions inside boost. Best regards, Fabien
fab wrote:
Hi, It would be a great thing to have a repository with all proposed gil extensions, and not only some zip files on adobe site.
Christian maintains extensions in his SVN repo @ Google Code http://code.google.com/p/gil-contributions/ You may want to look at this thread: http://lists.boost.org/Archives/boost/2009/10/156817.php http://lists.boost.org/Archives/boost/2009/10/156819.php
It would be a great thing to use global includes to boost gil in all extensions, like : #include <boost/gil/gil_all.hpp> and no : #include "../../boost/gil/gil_all.hpp" which imposes to copy this extensions inside boost.
I'd vote for - single header extentions #include <boost/gil/extensions/a.hpp> #include <boost/gil/extensions/b.hpp> - extentions with more complex structure #include <boost/gil/extensions/io/a.hpp> #include <boost/gil/extensions/numeric/a.hpp> I think it's a good approach and works well for Boost Geometry http://svn.boost.org/svn/boost/sandbox/geometry/boost/geometry/extensions/ Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org
Mateusz, qq. How does the Boost Geometry extensions work when they are referencing each other? For instance, gil::io_new includes some stuff from gil::toolbox. Meaning when someone checks out gil::io_new he/she would need to download toolbox, as well. The only solution, I can think of, is to check out all extensions at all time. Like we do with boost. When using boost we tend to have all of the boost code at hand and not a subset. I think we should make that a recommendation in the documentation. Regards, Christian On Wed, Mar 3, 2010 at 8:28 PM, Mateusz Loskot <mateusz@loskot.net> wrote:
fab wrote:
Hi, It would be a great thing to have a repository with all proposed gil extensions, and not only some zip files on adobe site.
Christian maintains extensions in his SVN repo @ Google Code
http://code.google.com/p/gil-contributions/
You may want to look at this thread:
http://lists.boost.org/Archives/boost/2009/10/156817.php http://lists.boost.org/Archives/boost/2009/10/156819.php
It would be a great thing to use global includes to boost gil in all extensions, like : #include <boost/gil/gil_all.hpp> and no : #include "../../boost/gil/gil_all.hpp" which imposes to copy this extensions inside boost.
I'd vote for
- single header extentions #include <boost/gil/extensions/a.hpp> #include <boost/gil/extensions/b.hpp>
- extentions with more complex structure #include <boost/gil/extensions/io/a.hpp> #include <boost/gil/extensions/numeric/a.hpp>
I think it's a good approach and works well for Boost Geometry http://svn.boost.org/svn/boost/sandbox/geometry/boost/geometry/extensions/
Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Christian Henning wrote:
Mateusz, qq. How does the Boost Geometry extensions work when they are referencing each other? For instance, gil::io_new includes some stuff from gil::toolbox. Meaning when someone checks out gil::io_new he/she would need to download toolbox, as well. The only solution, I can think of, is to check out all extensions at all time. Like we do with boost. When using boost we tend to have all of the boost code at hand and not a subset. I think we should make that a recommendation in the documentation.
So far, I have identified only two inter-extensions dependencies in Boost.Geometry. It is: 1) gis/projections use gis/geographic by including <boost/geometry/extensions/gis/geographic/strategies/dms_parser.hpp> 2) gis/latlong use gis/geographic by including <boost/geometry/extensions/gis/geographic/strategies/andoyer.hpp> In fact, we have not documented any recommendations for extensions users yet, but I suppose the approach of grabbing all extensions at once would be the simplest way to use them. However, it's a good idea to include information, in docs, that particular extension A requires extension B, C, ... So, user can makes its own way to install extensions. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org
participants (4)
-
Christian Henning -
Daniel James -
fab -
Mateusz Loskot