Author Topic: how to get back in the saddle (start working with codeblocks again)?  (Read 1139 times)

Offline bootstrap

  • Multiple posting newcomer
  • *
  • Posts: 64
I had to stop working on a long-term project (GCC plus 64-bit assembly language) on codeblocks about 8 months ago.

Not that long before I stopped, codeblocks stopped getting updated from the nightly-build repository.  A while before that I noticed the version switched to "svn 0"... in both the sign-on window when I start codeblocks and when I select "help -> about" in the CB menu-bar too.  I didn't worry about that because... CB was still working, more-or-less.  Note that the date on that last update (as indicated on that "help -> about" splash window) is "Build: Feb 28 2018, 06:28:15 - wx3.0.2 (linux, unicode) - 64-bit".  Oh, and I almost forgot to say, my computer runs "Linux Mint 17.3".

I'll be installing the latest Linux Mint 19.1 in a couple days and will need to get codeblocks running there and move my applications over to that fresh build.


My questions are:

#1:  Why did the version switch from "svn #####" (numbers in the thousands or tens of thousands as I recall) to "svn 0" back about a year or so ago?

#2:  Why did nightly builds stop getting uploaded from the repository?

#3:  How do I get the fresh new Linux Mint 19.1 installation to install everything and start getting updates from a repository (any repository)?

#4:  Has anything significant or major with codeblocks changed since a year ago?

As I said above, I only need to develop GCC (C/C++) and 64-bit assembly-language (in old ATT format, though might rewrite if the new format is well supported now).

#5:  So I guess another question is... is the new 64-bit assembly format now well accepted and assembled by the GNU compiler/assembler/linker/etc toolset?

In the meantime I switched over to the latest 8-core Ryzen CPU from the previous AMD CPUs (Bulldozer or Piledriver... whatever the one prior to Ryzen was).

#6:  Will codeblocks or any of the tools have any problems with Ryzen CPUs?

#7:  What are the appropriate "compiler, assembler, linker, tool" flags to indicate support for Ryzen CPUs?  I'll need to change them in my codeblocks files.

Thanks to whoever wants to bring me back up to date.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6636
    • My Best Post
Re: how to get back in the saddle (start working with codeblocks again)?
« Reply #1 on: January 05, 2019, 12:02:29 am »
svn of 0 means the builder do not have svn installed or the build system used by the builder can not find it.

Tim S.


« Last Edit: January 05, 2019, 02:06:12 am by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12005
    • Travis build status
Re: how to get back in the saddle (start working with codeblocks again)?
« Reply #2 on: January 05, 2019, 02:19:49 am »
1. The bootstrap script has problems, someone has to debug it or probably the person building the packages shouldn't call the bootstrap script.
2., 3. Ask the person maintaining your repo
4. We have a major update to the editor component
5. Ask your compiler vendor
6. Works fine, if your cpu is not from the first buggy batch like mine, but AMD would replace it...
7. Same as 5 - ask your compiler vendor, last time I looked the dedicated march for ryzen wasn't good.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline bootstrap

  • Multiple posting newcomer
  • *
  • Posts: 64
Re: how to get back in the saddle (start working with codeblocks again)?
« Reply #3 on: January 05, 2019, 06:17:37 pm »
When you say "we have a major update to the editor component"... do you mean that is already in, or coming soon?

Do any of you know anyone who has a repository for codeblocks that works on Linux Mint Cinnamon (any version from 17.3 to the current 19.1)?

My Ryzen 7 1800X was one of the first.  I haven't noticed problems... except for VLC freezes Linux sometimes when you skip to a new location, but I assume that is a problem in VLC.

I'll be getting a Zen 2 (Ryzen 9 3800/3850 or threadripper with maximum cores) when they become available, but until then march=znver1 looks like the correct setting.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12005
    • Travis build status
Re: how to get back in the saddle (start working with codeblocks again)?
« Reply #4 on: January 05, 2019, 07:14:21 pm »
When you say "we have a major update to the editor component"... do you mean that is already in, or coming soon?
You've asked what is new, I've told you. The changes are in the night builds for quite a while.

... but until then march=znver1 looks like the correct setting.
If you're using GCC then this is the wrong option, but I guess reading is hard. :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline bootstrap

  • Multiple posting newcomer
  • *
  • Posts: 64
Re: how to get back in the saddle (start working with codeblocks again)?
« Reply #5 on: January 06, 2019, 07:43:44 pm »
Reading is not hard... for me.

But knowing which of several sources knows what they're talking about often is.

Don't tell me you've never run into contradictory information on the internet!  :-o