Author Topic: rev 7954 screwsup big time  (Read 9598 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
rev 7954 screwsup big time
« on: May 08, 2012, 11:14:37 pm »
- hardly anymore toolbars : main and debugger
- logs & others : CB & search results

- start here page : no more nice names : stuff like : CB_TXT_NEW_PROJECT, ... , CB_VAR_RECENT_FILES_AND_PROJECTS
- list of recent projects/files : gone

in the CB log :
Quote
SDK version mismatch for HeaderFixup (1.13.2). Expecting 1.13.1
SDK version mismatch for DoxyBlocks (1.13.2). Expecting 1.13.1
SDK version mismatch for IncrementalSearch (1.13.2). Expecting 1.13.1
SDK version mismatch for BrowseTracker (1.13.2). Expecting 1.13.1
SDK version mismatch for ClassWizard (1.13.2). Expecting 1.13.1
SDK version mismatch for CB_Koders (1.13.2). Expecting 1.13.1
SDK version mismatch for ToolsPlus (1.13.2). Expecting 1.13.1
Tools Plus Plugin: Registering shell type Piped Process Control
SDK version mismatch for EditorTweaks (1.13.2). Expecting 1.13.1
SDK version mismatch for AutoVersioning (1.13.2). Expecting 1.13.1
SDK version mismatch for Valgrind (1.13.2). Expecting 1.13.1
SDK version mismatch for ToDoList (1.13.2). Expecting 1.13.1
SDK version mismatch for lib_finder (1.13.2). Expecting 1.13.1
SDK version mismatch for Compiler (1.13.2). Expecting 1.13.1
SDK version mismatch for CodeStat (1.13.2). Expecting 1.13.1
SDK version mismatch for wxSmithAui (1.13.2). Expecting 1.13.1
SDK version mismatch for Cccc (1.13.2). Expecting 1.13.1
SDK version mismatch for wxSmith (1.13.2). Expecting 1.13.1
SDK version mismatch for wxSmithMime (1.13.2). Expecting 1.13.1
SDK version mismatch for wxSmithContribItems (1.13.2). Expecting 1.13.1
SDK version mismatch for Abbreviations (1.13.2). Expecting 1.13.1
SDK version mismatch for SymTab (1.13.2). Expecting 1.13.1
SDK version mismatch for NassiShneidermanPlugin (1.13.2). Expecting 1.13.1
SDK version mismatch for ScriptedWizard (1.13.2). Expecting 1.13.1
SDK version mismatch for OpenFilesList (1.13.2). Expecting 1.13.1
SDK version mismatch for MouseSap (1.13.2). Expecting 1.13.1
SDK version mismatch for Debugger (1.13.2). Expecting 1.13.1
SDK version mismatch for RegExTestbed (1.13.2). Expecting 1.13.1
SDK version mismatch for AStylePlugin (1.13.2). Expecting 1.13.1
SDK version mismatch for BYOGames (1.13.2). Expecting 1.13.1
SDK version mismatch for cbKeyBinder (1.13.2). Expecting 1.13.1
SDK version mismatch for Profiler (1.13.2). Expecting 1.13.1
SDK version mismatch for cbDragScroll (1.13.2). Expecting 1.13.1
SDK version mismatch for ThreadSearch (1.13.2). Expecting 1.13.1
SDK version mismatch for FileManager (1.13.2). Expecting 1.13.1
SDK version mismatch for CodeCompletion (1.13.2). Expecting 1.13.1
SDK version mismatch for Cscope (1.13.2). Expecting 1.13.1
SDK version mismatch for SpellChecker (1.13.2). Expecting 1.13.1
SDK version mismatch for Exporter (1.13.2). Expecting 1.13.1
SDK version mismatch for ProjectsImporter (1.13.2). Expecting 1.13.1
SDK version mismatch for CppCheck (1.13.2). Expecting 1.13.1
SDK version mismatch for ReopenEditor (1.13.2). Expecting 1.13.1
SDK version mismatch for HelpPlugin (1.13.2). Expecting 1.13.1
SDK version mismatch for HexEditor (1.13.2). Expecting 1.13.1
SDK version mismatch for FilesExtensionHandler (1.13.2). Expecting 1.13.1
SDK version mismatch for EnvVars (1.13.2). Expecting 1.13.1
SDK version mismatch for CodeSnippets (1.13.2). Expecting 1.13.1
SDK version mismatch for copystrings (1.13.2). Expecting 1.13.1
SDK version mismatch for Autosave (1.13.2). Expecting 1.13.1

How did this happen :
1) have a nice working CB build before
2) svn up
3) make
4) sudo make install

Makes me bring out my favorite enemy again : did I get bitten once again by those f** pch's ????
If so, grrrrrrrrrr, then I want all pch's gone gone gone. They can go to hell, just give me old regular compilation techniques, those at least work.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: rev 7954 screwsup big time
« Reply #1 on: May 08, 2012, 11:55:04 pm »
Where are the bootstrap or configure calls?
What about cleaning the old install?

p.s. if you want use it this way it is best to use ./configure --prefix=/home/myname/software/cb/ and every new build you can ditch the old install easily.
« Last Edit: May 08, 2012, 11:56:42 pm by oBFusCATed »
(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 killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: rev 7954 screwsup big time
« Reply #2 on: May 09, 2012, 07:30:47 am »
off course : make clean, bootstap, configure, make , make install : and we are back in bizznizz. But doing this entire chain seems to be to much. Things should be simple : just make.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: rev 7954 screwsup big time
« Reply #3 on: May 09, 2012, 09:48:22 am »
For me it is just "emerge codeblocks" and it does all it needs to be done :)
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: rev 7954 screwsup big time
« Reply #4 on: May 09, 2012, 11:46:09 am »
Things should be simple : just make.
...or running C::B in batch mode on a WS file containing all projects you want to have in the nightly. ;-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: rev 7954 screwsup big time
« Reply #5 on: May 09, 2012, 12:04:34 pm »
...or running C::B in batch mode on a WS file containing all projects you want to have in the nightly. ;-)
Sorry but then you don't get the "make install" feature...

killerbot: If you can't remember the steps put them in a script. You can event try to build out-of-source-tree and to have the easy dump option.
« Last Edit: May 09, 2012, 01:17:02 pm by oBFusCATed »
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: rev 7954 screwsup big time
« Reply #6 on: May 09, 2012, 01:01:20 pm »
Sorry but then you don't get the "make install" feature...
I don't need this. I've put an alias into the .bashrc that points to the "output" folder's generated run.sh script that I've modified in a way that the LD_LIBRARY_PATH is setup properly. This way I don't even need root rights for a simple update of C::B. All it needs is batch-building C::B and running he update script and done (assuming you are the only person that want to work with C::B on that machine). This is a two liner that works very reliable for me on Linux and should work like that on any distro where you have C::B initially in addition.

Maybe that's a good hint for other people like me.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: rev 7954 screwsup big time
« Reply #7 on: May 09, 2012, 01:18:06 pm »
If you use --prefix you don't need root rights, too.
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: rev 7954 screwsup big time
« Reply #8 on: May 09, 2012, 01:24:21 pm »
If you use --prefix you don't need root rights, too.
You/we know this, but a newbie doesn't. This is information for being able to compile C::B in a most easiest, least error-prone way. It is intended for Linux non-experts (like me).
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: rev 7954 screwsup big time
« Reply #9 on: May 09, 2012, 01:29:12 pm »
I know does commands, don't worry.
All I am saying is that our build infrastructure is NOT reliable, meaning : it should work in a simple incremental way. Assuming that no extra plug-ins got added, and only existing code changes, there should be no requirement on doing "bootstrap and configure", plain make/make install should be sufficient. And it is not, it requires you to go back to the very basic start.

I will repeat this : when the only things one is doing is modifying existing code, an incremental build HAS TO work. That's the way software should build, all the rest are excuses and crap.

I don't recall what my previous version was one, but looking at the last bunch of commits, only existing code got changed (should further investigate).

Same when one would build by using the cbp's files. Then you actually don't know what bootstrap/configure is ;-), you build and call update.

when "make" or "pressing build button" in CB is not sufficient to build (when no new plug-ins,libraries are added), plain simple : build system is wrong.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: rev 7954 screwsup big time
« Reply #10 on: May 09, 2012, 01:55:56 pm »
Same when one would build by using the cbp's files. Then you actually don't know what bootstrap/configure is ;-), you build and call update.

when "make" or "pressing build button" in CB is not sufficient to build (when no new plug-ins,libraries are added), plain simple : build system is wrong.
The difference is that the ./configure handles many systems and handles dependencies, C::B's build system doesn't.
I don't know what has happened on your system, probably some dependencies are not handled. If you can reproduce the problem we can try to fix it.
Probably update back to r7920, do a full clean build, update again and do another build with make only.
Also keep in mind that make uninstall is pretty useless...

I generally follow the boostrap/configure/make/make install command chain, when I want create installable versions of C::B and I have no problems.
I do this in order to get a reliable version of C::B.

And after an update I always do a full rebuild even using C::B's build system, just in case.

Another thing, it is always better to build packages for the distribution you're on instead of using make/make install directly.
I do this both on gentoo (where I have an svn ebuild) and on centos(where I use rpmbuild to build rpms).
I guess Jens could post the steps needed to build debian packages.
This is the most reliable way to install software on linux. If you don't like it use windows or macosx (the drag and drop territory).

p.s. you reminded me that I've forgotten to fix the Makefile.am in my last commit...
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: rev 7954 screwsup big time
« Reply #11 on: May 09, 2012, 04:50:26 pm »
Probably update back to r7920, do a full clean build, update again and do another build with make only.
Maybe its even easier: Just pump the SDK version temporarily, hit make (only) and have a look if it fails at runtime. I have that weird feeling that this is the root of the evil.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline Jenna

  • Administrator
  • Lives here!
  • *****
  • Posts: 7255
Re: rev 7954 screwsup big time
« Reply #12 on: May 10, 2012, 01:21:00 am »
I guess Jens could post the steps needed to build debian packages.
dpkg-buildpackage in the root of C::B's (svn-)sources (the folder where the debian subfolder is).
The debs are in the folder wher C::B's root folder is located.
You might need to run ./update_revision.sh to update debian/changelog to have the correct svn-version in the packagenames.

Offline daniloz

  • Regular
  • ***
  • Posts: 268
Re: rev 7954 screwsup big time
« Reply #13 on: May 11, 2012, 10:16:48 am »
Sorry for the (bit) OT question, but...

Is there a way to do anything similar to a "command-line linux make" in Windows to build C::B (core project and plugins project) after an svn update? I mean, just opening a console and typing something like "make" to do the whole process.

You can assume that I have both cygwin and msys running on my system. :-)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: rev 7954 screwsup big time
« Reply #14 on: May 11, 2012, 10:38:56 am »
If you have working codeblocks, you should be able to use it in batch mode.
Otherwise there was a patch for the autotools system for building mingw32 binaries on linux.
I guess you can search for it and see if it makes the autotools system usable under cygwin, but I doubt it.
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: rev 7954 screwsup big time
« Reply #15 on: May 11, 2012, 02:53:55 pm »
Is there a way to do anything similar to a "command-line linux make" in Windows to build C::B (core project and plugins project)
Use the batch files:
batch_build_core.bat
batch_build_plugins.bat
...provided via SVN. All you need to do it to adjust the path to Code::Blocks and the compiler in these files.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ