Re: Upgrade to boost 1.59?

2015-11-02 Thread Peter Kümmel

Am 02.11.2015 um 11:40 schrieb Jean-Marc Lasgouttes:

Le 01/11/2015 16:51, Scott Kostyshak a écrit :

On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote:

Am 25.10.2015 um 06:19 schrieb Scott Kostyshak:

On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote:


I have it documented somewhere. Should I put it in development.lyx ?


If you are able to find it easily then I would say yes, please do. Even
though Peter already did the update it could be useful in the future.

Scott



Just call in boost extract.sh with the path to the new boot version,
then "git add --all", commit. That's it.


Thanks, Peter. It is good to know it is so straightforward.


Can it happen that we should remove some of the files too?


The scripts removes all existing files and adds all found by bcp.
Four files were deleted, ( git diff 04be61ea8 --name-status | grep D )

But bcp is called with these headers:

boost/any.hpp \
boost/assert.hpp \
boost/bind.hpp \
boost/crc.hpp \
boost/cstdint.hpp \
boost/format.hpp \
boost/function.hpp \
boost/functional.hpp \
boost/lexical_cast.hpp \
boost/noncopyable.hpp \
boost/regex.hpp \
boost/scoped_array.hpp \
boost/scoped_ptr.hpp \
boost/shared_ptr.hpp \
boost/signal.hpp \
boost/signals/connection.hpp \
boost/signals/trackable.hpp \
boost/tokenizer.hpp \
boost/tuple/tuple.hpp \
boost/mpl/string.hpp \
boost/mpl/fold.hpp \
boost/mpl/size_t.hpp \
boost/functional/hash.hpp \

so, when something has changed there, then we have
too much headers in our repository.



But indeed, thanks for updating.

JMarc






Re: Upgrade to boost 1.59?

2015-11-02 Thread Jean-Marc Lasgouttes

Le 01/11/2015 16:51, Scott Kostyshak a écrit :

On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote:

Am 25.10.2015 um 06:19 schrieb Scott Kostyshak:

On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote:


I have it documented somewhere. Should I put it in development.lyx ?


If you are able to find it easily then I would say yes, please do. Even
though Peter already did the update it could be useful in the future.

Scott



Just call in boost extract.sh with the path to the new boot version,
then "git add --all", commit. That's it.


Thanks, Peter. It is good to know it is so straightforward.


Can it happen that we should remove some of the files too?

But indeed, thanks for updating.

JMarc



Re: Upgrade to boost 1.59?

2015-11-02 Thread Jean-Marc Lasgouttes

Le 02/11/2015 12:34, Peter Kümmel a écrit :

The scripts removes all existing files and adds all found by bcp.
Four files were deleted, ( git diff 04be61ea8 --name-status | grep D )


OK, thanks.


But bcp is called with these headers:

[...]

so, when something has changed there, then we have
too much headers in our repository.


Indeed.

JMarc



Re: Upgrade to boost 1.59?

2015-11-01 Thread Vincent van Ravesteijn
On Sun, Nov 1, 2015 at 4:51 PM, Scott Kostyshak  wrote:
> On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote:
>> Am 25.10.2015 um 06:19 schrieb Scott Kostyshak:
>> >On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote:
>> >
>> >>I have it documented somewhere. Should I put it in development.lyx ?
>> >
>> >If you are able to find it easily then I would say yes, please do. Even
>> >though Peter already did the update it could be useful in the future.
>> >
>> >Scott
>> >
>>
>> Just call in boost extract.sh with the path to the new boot version,
>> then "git add --all", commit. That's it.
>
> Thanks, Peter. It is good to know it is so straightforward.
>
> Scott

It's only that simple if you have installed the bcp utility.

I have made a script that automatically downloads the latest boost,
unpacks the tar, compiles bcp, and uses it when running the extract
script. I'll share it later.

Vincent


Re: Upgrade to boost 1.59?

2015-11-01 Thread Scott Kostyshak
On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote:
> Am 25.10.2015 um 06:19 schrieb Scott Kostyshak:
> >On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote:
> >
> >>I have it documented somewhere. Should I put it in development.lyx ?
> >
> >If you are able to find it easily then I would say yes, please do. Even
> >though Peter already did the update it could be useful in the future.
> >
> >Scott
> >
> 
> Just call in boost extract.sh with the path to the new boot version,
> then "git add --all", commit. That's it.

Thanks, Peter. It is good to know it is so straightforward.

Scott


Re: Upgrade to boost 1.59?

2015-11-01 Thread Peter Kümmel
Using bcp from older boost releases also works, so the one from your package 
manager should be enough.
Peter 

Am 1. November 2015 17:42:51 MEZ, schrieb Vincent van Ravesteijn :
>On Sun, Nov 1, 2015 at 4:51 PM, Scott Kostyshak 
>wrote:
>> On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote:
>>> Am 25.10.2015 um 06:19 schrieb Scott Kostyshak:
>>> >On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn
>wrote:
>>> >
>>> >>I have it documented somewhere. Should I put it in development.lyx
>?
>>> >
>>> >If you are able to find it easily then I would say yes, please do.
>Even
>>> >though Peter already did the update it could be useful in the
>future.
>>> >
>>> >Scott
>>> >
>>>
>>> Just call in boost extract.sh with the path to the new boot version,
>>> then "git add --all", commit. That's it.
>>
>> Thanks, Peter. It is good to know it is so straightforward.
>>
>> Scott
>
>It's only that simple if you have installed the bcp utility.
>
>I have made a script that automatically downloads the latest boost,
>unpacks the tar, compiles bcp, and uses it when running the extract
>script. I'll share it later.
>
>Vincent

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Upgrade to boost 1.59?

2015-10-31 Thread Peter Kümmel

Am 25.10.2015 um 06:19 schrieb Scott Kostyshak:

On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote:


I have it documented somewhere. Should I put it in development.lyx ?


If you are able to find it easily then I would say yes, please do. Even
though Peter already did the update it could be useful in the future.

Scott



Just call in boost extract.sh with the path to the new boot version,
then "git add --all", commit. That's it.

Peter


Re: Upgrade to boost 1.59?

2015-10-24 Thread Scott Kostyshak
On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote:

> I have it documented somewhere. Should I put it in development.lyx ?

If you are able to find it easily then I would say yes, please do. Even
though Peter already did the update it could be useful in the future.

Scott


Upgrade to boost 1.59?

2015-10-23 Thread Jean-Marc Lasgouttes
I think we should upgrade our local copy of boost to 1.59 before alpha 
(or at least before beta).


Is the procedure documented somewhere?

Also, what can we do to hide the warnings related to auto_ptr? If we are 
out of ideas, I propose to compile with -Wno-deprecated-functions in 
C++11 mode.


JMarc


Re: Upgrade to boost 1.59?

2015-10-23 Thread Vincent van Ravesteijn
Op 23 okt. 2015 17:37 schreef "Jean-Marc Lasgouttes" :
>
> I think we should upgrade our local copy of boost to 1.59 before alpha
(or at least before beta).
>
> Is the procedure documented somewhere?
>
> Also, what can we do to hide the warnings related to auto_ptr? If we are
out of ideas, I propose to compile with -Wno-deprecated-functions in C++11
mode.
>
> JMarc

I have it documented somewhere. Should I put it in development.lyx ?

Vincent


Re: Upgrade to boost 1.59?

2015-10-23 Thread Peter Kümmel



Am 23.10.2015 um 18:13 schrieb Vincent van Ravesteijn:


Op 23 okt. 2015 17:37 schreef "Jean-Marc Lasgouttes"
>:
 >
 > I think we should upgrade our local copy of boost to 1.59
before alpha (or at least before beta).
 >
 > Is the procedure documented somewhere?
 >
 > Also, what can we do to hide the warnings related to
auto_ptr? If we are out of ideas, I propose to compile with
-Wno-deprecated-functions in C++11 mode.
 >
 > JMarc

I have it documented somewhere. Should I put it in
development.lyx ?

Vincent



I could do it. I've done it already multiple times.

Peter

(a little, little back ;)