[packaging] libapr README url fix patch

Dale Lukas Peterson hazelnusse at gmail.com
Thu Apr 4 01:46:35 UTC 2019

Hi Boris,
 I've been trying to get this finished and have a start here:

I don't think I have fully wrapped my head around bulid2 so I probably have
something not quite correct. In particular I don't know if I've got the
export.build2 stuff correct or quite how to test it. I think probably I
need to create a simple application that depends on catch2, following the
example in the manual and see if what I've done works correctly?

About the only thing I've done is to verify that the result of `b install`
looks reasonable, and I think it does:
[I] luke at t480s ~/r/C/Catch2> t /tmp/install
├── include
│   └── catch2
│       └── catch.hpp
├── lib
│   └── pkgconfig
│       ├── libCatch2.shared.pc
│       └── libCatch2.static.pc
└── share
    └── doc
        └── Catch2
            ├── LICENSE.txt
            ├── manifest
            └── README.md

7 directories, 6 files

I do have 2 questions:
1) the pkgconfig files have the following lines:
Libs: -L/tmp/install/lib
Is this desired for header only libraries?

2) I made the name in the manifest as well as the project in the
boostrap.build both be Catch2. Experimentally it seems that the project =
Catch2 from bootstrap.build is used to name the directory where the
LICENSE.txt, manifest, and README.md go. I was a bit confused by this and
wonder if you could explain when you might have different values for the
name and the project?

If you think it makes sense for me to create a pull request now to Catch2,
I can do so and we can continue discussion on the PR -- I just wasn't sure
how far I am from what would be reasonable to call "done" on this. I took a
look at the Catch2 python script used to create a single header... and hmm.
Not sure I have time to go there at the moment.


On Thu, Mar 7, 2019 at 6:35 AM Boris Kolpackov <boris at codesynthesis.com>

> Dale Lukas Peterson <hazelnusse at gmail.com> writes:
> >  Things got busy at work. I haven't forgotten about this but it will
> > likely be the weekend before I can come back to it.
> No problem.
> I have added support for an alternative build file/directory naming
> scheme and it is now available in the staged toolchain[1]. Here is
> the relevant part from the manual:
> "
> It is also possible to use an alternative build file/directory naming
> scheme where every instance of the word 'build' is replaced with 'build2',
> for example:
> hello/
> ├── build2/
> │   ├── bootstrap.build2
> │   └── root.build2
> ├── ...
> └── build2file
> Note that the naming must be consistent within a project with all the
> filesystem entries either following 'build' or 'build2' scheme. In other
> words, we cannot call the directory build2/ while keep using buildfile.
> The alternative naming scheme is primarily useful when adding build2
> support to an existing project along with other build systems. In this
> case, the fairly generic standard names might already be in use. For
> example, it is customary to have build/ in .gitignore. Plus more
> specific naming will make it easier to identify files and directories
> as belonging to the build2 support. For new projects as well as for
> existing project that are switching exclusively to build2 the standard
> naming scheme is recommended.
> To create a project with the alternative naming using bdep-new(1) pass
> the  alt-naming project type sub-option. For example:
> $ bdep new -t exe,alt-naming ...
> "
> I think we should use this alternative scheme for Catch2 in order to
> sidestep all those .gitignore issues.
> [1] https://stage.build2.org/0/

For a successful technology, reality must take precedence over public
relations, for Nature cannot be fooled. -- Richard Feynman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.build2.org/archives/packaging/attachments/20190403/a7093ca7/attachment.html>

More information about the packaging mailing list