Re: [boost] [Boost-users] [Fit] upcoming formal review for Boost.Fit

Subject: Re: [boost] [Boost-users] [Fit] upcoming formal review for Boost.Fit
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2016-02-29 17:56:52

Le 29/02/2016 19:12, Paul Fultz II a écrit :
>
>
> On Monday, February 29, 2016 at 1:13:06 AM UTC-6, Vicente J. Botet 
> Escriba wrote:
>
>     Le 29/02/2016 05:37, Paul Fultz II a écrit :
>     >
>     >
>     > On Sunday, February 28, 2016 at 5:28:39 PM UTC-6, Edward Diener
>     wrote:
>     >
>     >     On 2/28/2016 4:23 PM, paul Fultz wrote:
>     >     >
>     >     >
>     >     >
>     >     >
>     >     > On Sunday, February 28, 2016 12:23 PM, Edward Diener
>     >     <eldi..._at_[hidden] <javascript:>> wrote:
>     >     >
>     >     >
>     >     >>
>     >     >>
>     >     >> On 2/27/2016 11:16 AM, Vicente J. Botet Escriba wrote:
>     >     >>> Dear Boost community,
>     >     >>>
>     >     >>> The formal review of Paul Fultz II's Fit library starts on
>     >     Wednesday, 2nd March and ends on 13th March.
>     >     >>
>     >     >> How do I generate the docs or run the tests for my local
>     copy
>     >     of Fit ?
>     >     >
>     >     >>
>     >     >
>     >     > You can build and run the tests by building the check target.
>     >     For those
>     >     > unfamiliar with cmake, first configure the build directory
>     with
>     >     cmake:
>     >     >
>     >     > mkdir build
>     >     > cd build
>     >     > cmake ..
>     >     > cd ..
>     >     >
>     >     > Next build the check target using the native build
>     system(such
>     >     as make or
>     >     > msbuild). CMake can call the native build system to build the
>     >     target 'check',
>     >     > like so:
>     >     >
>     >     > cmake --build build --config Release --target check
>     >     >
>     >     > Also, the library can be installed by invoking the 'install'
>     >     target.
>     >
>     >     Why is the CMakeLists.txt not in the 'test' subdirectory,
>     since it
>     >     appears from your explanation that the file is used for the
>     tests ?
>     >
>     >
>     > Its used to install the library as well.
>     >
>     >
>     >     >
>     >     > The documentation needs to be built using mkdocs. You can
>     >     install mkdocs and
>     >     > the boost theme with pip like this:
>     >     >
>     >     > pip install mkdocs mkdocs-boost
>     >     >
>     >     > Then to build the documentation, first `setup.py` must be
>     run to
>     >     extract the
>     >     > documentation and examples from the source code, then
>     `mkdocs`
>     >     can be invoked,
>     >     > like this:
>     >     >
>     >     > python setup.py
>     >     > mkdocs build -t boost
>     >     >
>     >     > And the documentation will be in the 'doc/html' directory.
>     >
>     >     Please add these explanations to Fit as you are not using Boost
>     >     build to
>     >     build the doc or run the tests.
>     >
>     >
>     > I will add them.
>     >
>     > Also, I tried to add an initial Jamfile to build and run the
>     tests as
>     > well. I
>     > just modified the Jamfile from other boost libraries. However, I
>     haven't
>     > figured out how to run the tests yet using bjam to test my
>     Jamfile. I get
>     > "error: Did not find Jamfile.jam or Jamroot.jam in any parent
>     > directory". I am
>     > not sure how I am supposed to run the tests.
>     You can try to copy the ones in https://github.com/viboes/std-make
>     <https://github.com/viboes/std-make>
>
>     I will try to help you this evening,
>
>
> Thanks for the help, I got a working bjam there to build the tests. Of 
> course,
> the next thing to do is to add them to the CI. However, it seems that 
> other
> boost libraries only tests using cmake. I will look into that further.
>
You will have time to add it to the CI once the library is approved ;-)
Or were you talking of your own CI?

Do you have an example of a library using cmake and not jamfile?

Vicente
Vicente