News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Information of SDK version into Nightly to track changes?

Started by LETARTARE, February 01, 2015, 04:38:55 PM

Previous topic - Next topic
Print
Go Down Pages1 2 All
User actions

LETARTARE

February 01, 2015, 04:38:55 PM
Hello,
would it be possible to provide for each new 'Nightly builds' the reference SDK ?
Regards.
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

MortenMacFly

#1
February 02, 2015, 08:09:36 PM Last Edit: February 02, 2015, 08:11:14 PM by MortenMacFly
@LETARTARE: For windows you can use the nightly itself and the sources of that revision from svn. It's explained in the wiki.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

LETARTARE

#2
February 03, 2015, 10:15:50 AM
Thanks you MortenMacFly,
I try to make the SDK change history, but it is laborious...
Also, write the version of the SDK in ads nightly builds, easily could track its evolution, to adapt the plugins.
Regards.
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

MortenMacFly

#3
February 04, 2015, 09:22:31 AM
Quote from: LETARTARE on February 03, 2015, 10:15:50 AM
I try to make the SDK change history, but it is laborious...
Ok. BTW: You can get the current SDK version from inside C::B using Help -> About -> Tab "Information".
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

LETARTARE

#4
February 04, 2015, 09:59:03 AM
@MortenMacFly
yes,
but to find the versions change SDK, must
1- update from the repository
2-check in 'cbplugin.h'
3-start with the following (or previous) nightly to find the change
and so on ...

Also, for future, it would be much easier, provide the SDK in the ads.

The best would be to open a new topic or each could provide information ??
What about you ?

Thanks you.
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

MortenMacFly

#5
February 04, 2015, 01:05:50 PM
Quote from: LETARTARE on February 04, 2015, 09:59:03 AM
The best would be to open a new topic or each could provide information ??
What about you ?
Splitted the topic and moved it into Development.

@killerbot: Do you think you could extend your template for the nightlies accordingly?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

killerbot

#6
February 04, 2015, 09:13:45 PM
will do, if I don't forget, so you might have to remind me  ;D

LETARTARE

#8
February 04, 2015, 11:20:56 PM
Thank you all.
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

LETARTARE

#9
February 05, 2015, 11:27:17 AM Last Edit: February 06, 2015, 03:46:15 PM by LETARTARE
Here's a little early list:

  • svn 806    sdk 1.0.0   1.0  2005-08-25
  • svn ?????    sdk 1.10.0
  • svn 4924   sdk 1.11.12    8.02  2008-03-01
  • svn 6335   sdk 1.11.12    10.05  2010-06-08
  • svn 7789   sdk 1.11.18
  • svn ?????    sdk 1.12.0
  • svn 8500   sdk 1.13.11
  • svn 8549   sdk 1.13.14
  • svn 8629   sdk 1.13.14    12.11  2012-11-28
  • svn ?????    sdk 1.14.0
  • svn 8818   sdk 1.15.0
  • svn ?????    sdk 1.16.0
  • svn 9156   sdk 1.17.0
  • svn 9232   sdk 1.18.0
  • svn 9501   sdk 1.19.0      13.12  2013-12-27
  • svn 9639   sdk 1.20.0
  • svn ?????    sdk 1.21.0
  • svn ?????    sdk 1.22.0
  • svn 9778   sdk 1.23.0
  • svn 10091  sdk 1.24.0
If you have additional information I will add ...
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

MortenMacFly

#10
February 05, 2015, 08:41:28 PM
Quote from: LETARTARE on February 05, 2015, 11:27:17 AM
If you have additional information I will add ...
For the missing SDK revisions you should check the branches (cc re-factoring, debugging, compiler framework re-design...). These are available trough SVN as well.

However, these have no meaning with respect to trunk, so you can safely skip them in the list.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

LETARTARE

#11
February 06, 2015, 04:08:02 PM
@MortenMacFly
thank you very much, I adapted the list accordingly.
Later, I will carry this list to:
http://wiki.codeblocks.org/index.php?title=Code::Blocks_SDK_events#List_of_Available_Code::Blocks_Events
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

ollydbg

#12
February 07, 2015, 06:30:59 AM Last Edit: February 07, 2015, 07:53:58 AM by ollydbg
Quote from: LETARTARE on February 05, 2015, 11:27:17 AM
Here's a little early list:

  • svn 806    sdk 1.0.0   1.0  2005-08-25
  • svn ?????    sdk 1.10.0
  • svn 4924   sdk 1.11.12    8.02  2008-03-01
  • svn 6335   sdk 1.11.12    10.05  2010-06-08
  • svn 7789   sdk 1.11.18
  • svn ?????    sdk 1.12.0
  • svn 8500   sdk 1.13.11
  • svn 8549   sdk 1.13.14
  • svn 8629   sdk 1.13.14    12.11  2012-11-28
  • svn ?????    sdk 1.14.0
  • svn 8818   sdk 1.15.0
  • svn ?????    sdk 1.16.0
  • svn 9156   sdk 1.17.0
  • svn 9232   sdk 1.18.0
  • svn 9501   sdk 1.19.0      13.12  2013-12-27
  • svn 9639   sdk 1.20.0
  • svn ?????    sdk 1.21.0
  • svn ?????    sdk 1.22.0
  • svn 9778   sdk 1.23.0
  • svn 10091  sdk 1.24.0
If you have additional information I will add ...
I think the above information is not correct. I just try to use git to find the SDK changes
Code Select

git log -p -- src/include/cbplugin.h -S"PLUGIN_SDK_VERSION_MINOR" >> result.txt

Then, I just search the result.txt with "+#define PLUGIN_SDK_VERSION_MINOR", I get the result:
Code Select

PLUGIN_SDK_VERSION_MINOR -> revision
24, 10050
23, 9767
22, 9763
21, 9759
20, 9606
19, 9283
18, 9204
....


EDIT:
Some post says "-S" option should be replaced by "-G", see: git -S VS -G, but in my testing environment (msysgit 1.9.5), I don't see there differences.

EDIT2:
I just check the result.txt, I see that my command
Code Select
git log -p -- src/include/cbplugin.h -S"PLUGIN_SDK_VERSION_MINOR" >> result.txt
don't do any search of the keyword of commits, it just blindly print all the diffs of each commits in the history of cbplugin.h.  :(

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

LETARTARE

#13
February 07, 2015, 10:04:37 AM Last Edit: September 21, 2017, 04:09:22 PM by LETARTARE
Thanks ollydbg, here are corrections :

  • svn 806    sdk 1.0.0   1.0  2005-08-25
  • svn ?????    sdk 1.10.0
  • svn 4924   sdk 1.11.12    8.02  2008-03-01
  • svn 6335   sdk 1.11.12    10.05  2010-06-08
  • svn 7789   sdk 1.11.18
  • svn ?????    sdk 1.12.0
  • svn 8500   sdk 1.13.11
  • svn 8549   sdk 1.13.14
  • svn 8629   sdk 1.13.14    12.11  2012-11-28
  • svn ?????    sdk 1.14.0
  • svn 8818   sdk 1.15.0
  • svn ?????    sdk 1.16.0
  • svn 9156   sdk 1.17.0
  • svn 9204   sdk 1.18.0
  • svn 9283   sdk 1.18.0
  • svn 9501  sdk 1.19.0      13.12  2013-12-27
  • svn 9606   sdk 1.20.0
  • svn 9759   sdk 1.21.0
  • svn 9763   sdk 1.22.0
  • svn 9767   sdk 1.23.0
  • svn 10050 sdk 1.24.0
  • svn 10136 sdk 1.25.0
  • svn 10474 sdk 1.26.0
  • svn 10503 sdk 1.27.0
  • svn 10528 sdk 1.28.0
  • svn 10553 sdk 1.29.0
  • svn 10762 sdk 1.30.0
  • svn 11135 sdk 1.31.0

I board never used these commands,  I just use Tortoisesvn to recover nightly.
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

ollydbg

#14
February 07, 2015, 02:53:38 PM
Hi, LETARTARE.
Here are the missing revisions:
Code Select

PLUGIN_SDK_VERSION_MINOR -> revision
24, 10050
23, 9767
22, 9763
21, 9759
20, 9606
19, 9283
18, 9204
17, 8899
16, 8898
15, 8798
14, 8177
13, 7920
12, note we don't have 12, we just change from 11 to 13 in rev 7920
11, 3594
10, 2983
9, 2863
8, 2658
7, 2347
6, 1422
5, 1414
4, 1340
3, note we don't have 3, we just change from 2 to 4 in rev 1340
2, 974
1, 949
0, 203


I finally use the correct git command to do the search:
Code Select

git log -G"#define PLUGIN_SDK_VERSION_MINOR" -p --follow src/include/cbplugin.h >> result.txt

You see, git is so powerful!

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.
Print
Go Up Pages1 2 All
User actions