Hello Mirek

What will be the improvements and where do you expect the compatibility problems may appear?

koldo wrote on Wed, 04 May 2016 09:38

Hello Mirek

What will be the improvements and where do you expect the compatibility problems may appear?

I will detail changes soon (but mostly it is about C++11 and multithreading).

So far, apart for one or two minor changes, suprisingly the most compatibility problems are caused by new Core detecting subtle bugs.

It took me 5 minutes to fix those is my largest app.

Mirek

Today I've spent like 5 minutes trying to find the function that copies text to clipboard, only to find that in CtrlCore.h there are things like ClearClipboard and WriteClipboardUnicodeText. Things like this should really be Clipboard::Clear and Clipboard::Write.

Hi Mirek,

I have updated the packaging to use C++11, but TheIDE build still fail. The error says DeepClone is not declared, you can see it in the build logs, e.g. for Debian Wheezy. Could you have a look at it, please?

Honza

Most likely it is missing MT in main package config.

mirek wrote on Sun, 08 May 2016 06:31

Most likely it is missing MT in main package config.

Oh, right, I missed that it is necessary now.

So the situation is much better now. There is just few problems left:

Ubuntu 12.4 and ScientificLinux 6 both fail, because their compiler (GCC 4.6 and 4.7, respectively) is so old it doesn't even support the option -std=c++11. Also the compiler in Debian Wheezy (GCC 4.7) doesn't work. This one already knows c++11, but thread_local keyword is not implemented, so the compilation fails.

And the last problem is in ArchLinux packages where the compilation fails on conflicting declaration of abs(int64), which is already present in stdlib in C++11.

Is it safe to drop support for the old distros, even though they are still supported? Ubuntu 12.4 has end-of-life scheduled for April 2017, Debian Wheezy has LTS until May 2018 and ScientificLinux 6 even has full support until Q2 2017 (and then maintenance updates until November 2020).

Honza

I tried to compile last version (upp-x11-src-9809.tar.gz) from source but it failed with lack of std=c++11.
Where it should be added?
src/Makefile?
src/Makefile.in?
src/UMakefile?

dolik.rce wrote on Sun, 08 May 2016 15:37

Is it safe to drop support for the old distros, even though they are still supported? Ubuntu 12.4 has end-of-life scheduled for April 2017, Debian Wheezy has LTS until May 2018 and ScientificLinux 6 even has full support until Q2 2017 (and then maintenance updates until November 2020).

Perhaps we can switch it to 'classic'?

mirek wrote on Mon, 09 May 2016 11:23

dolik.rce wrote on Sun, 08 May 2016 15:37

Is it safe to drop support for the old distros, even though they are still supported? Ubuntu 12.4 has end-of-life scheduled for April 2017, Debian Wheezy has LTS until May 2018 and ScientificLinux 6 even has full support until Q2 2017 (and then maintenance updates until November 2020).

Perhaps we can switch it to 'classic'?

It could be done, if you package the 'classic' uppsrc into the nigthly tarball.

dolik.rce wrote on Mon, 09 May 2016 16:32

mirek wrote on Mon, 09 May 2016 11:23

dolik.rce wrote on Sun, 08 May 2016 15:37

Is it safe to drop support for the old distros, even though they are still supported? Ubuntu 12.4 has end-of-life scheduled for April 2017, Debian Wheezy has LTS until May 2018 and ScientificLinux 6 even has full support until Q2 2017 (and then maintenance updates until November 2020).

Perhaps we can switch it to 'classic'?

It could be done, if you package the 'classic' uppsrc into the nigthly tarball.

Well, I do not. 'classic' is basically branch for systems not supporting C++11.

I perhaps could generate complete 'classic' tarball.

Maybe the package should be left as is, and upp2 can be introduced? (like kde4 vs kde5 during transition period)
Or that's too complicated to maintain either?

mirek wrote on Mon, 09 May 2016 17:25

dolik.rce wrote on Mon, 09 May 2016 16:32

mirek wrote on Mon, 09 May 2016 11:23

dolik.rce wrote on Sun, 08 May 2016 15:37

Is it safe to drop support for the old distros, even though they are still supported? Ubuntu 12.4 has end-of-life scheduled for April 2017, Debian Wheezy has LTS until May 2018 and ScientificLinux 6 even has full support until Q2 2017 (and then maintenance updates until November 2020).

Perhaps we can switch it to 'classic'?

It could be done, if you package the 'classic' uppsrc into the nigthly tarball.

Well, I do not. 'classic' is basically branch for systems not supporting C++11.

I perhaps could generate complete 'classic' tarball.

I understand that it is a branch, but I think it could still be present in the tarball as a "fallback" for older systems. It would also be simpler for the users, because having two tarballs requires explaining them in great detail which one they should use...
Honza