Code::Blocks

Developer forums (C::B DEVELOPMENT STRICTLY!) => Plugins development => Topic started by: LETARTARE on February 10, 2015, 05:53:03 pm

Title: a new plugin : QtPregenForCB
Post by: LETARTARE on February 10, 2015, 05:53:03 pm
Hello everyone,
I suggest a plugin for compiling Qt project using Code::Blocks .
This extension of  Code::Blocks will be offered on:
https://github.com/LETARTARE/QtPregenForCB (https://github.com/LETARTARE/QtPregenForCB)
and is called :
Quote
QtPregenForCB-0.2.2

If this plugin interested persons, I would do an article in the Wiki.

See the discussion: http://forums.codeblocks.org/index.php/topic,19931.0.html (http://forums.codeblocks.org/index.php/topic,19931.0.html)
Sincerely
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 11, 2015, 09:20:32 am
Hello,
I forgot to provide patches for 'Code::Blocks'  (svn 9501, 10035, 10091)  !!
It is repaired.
https://github.com/LETARTARE/QtPregenForCB
Sincerely
Title: Re: a new plugin : QtPregenForCB
Post by: MortenMacFly on February 11, 2015, 06:30:55 pm
I forgot to provide patches for 'Code::Blocks'  (svn 9501, 10035, 10091)  !!
...in SVN. I see no reason why we should not do this. However, keep the comments of obfuscated in mind... To be bullet-proof the event ID's should be standardised and exposed through the SDK. So this actually is only half of the way...
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 11, 2015, 09:03:49 pm
I still don't think this is a good solution, in fact I think this is terrible solution and if it was up to me I'd revert it.

For example the current version of the plugin will break if the user uses the context menu in the project manager.
It will break, if the compilation is started by a script. Or even from the debugger.

If you need to know something like a reason why the event has been fired then we should use some kind enum for the task.
Title: Re: a new plugin : QtPregenForCB
Post by: MortenMacFly on February 11, 2015, 09:40:13 pm
If you need to know something like a reason why the event has been fired then we should use some kind enum for the task.
Thats what I meant with:
To be bullet-proof the event ID's should be standardised and exposed through the SDK.
However, in the compiler you'd then only replace the int ID with an enum ID. Therefore the code is "kind of" valid. I didn't state that its correct to use the ID's as done in the plugin.
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 11, 2015, 11:51:10 pm
But still how do you know that the value of the m_EventId is set correctly before we the event is fired?
There is no code to reset it. So if the event is fired from a different code-path than the one expected it will be fired with invalid information.

Shouldn't we add more fine grained events that make the implementation of this plugin possible?

From the code of the plugin I can see that it is interested to know if a project is cleaned, built or if a single file is compiled (but does nothing in this case).

Should I revert this commit or you'll do it?  8)
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 12, 2015, 07:01:06 pm
Hello,
thank you very much to both of you for your advice.
@MortenMacFly
Thanks for the commit to svn 10115  :)

@oBFusCATed
I'm not sure I understood ?
Quote
For example the current version of the plugin will break if the user uses the context menu in the project manager.
because actually I can use the context menu 'Build, Rebuild, Clean' with no break.

Quote
From the code of the plugin I can see that it is interested to know if a project is cleaned, built or if a single file is compiled (but does nothing in this case).
Yes, it is exactly that. For a single file I still wonder about the work to be done?

Anyway, if you have a different solution, with the current svn, I take.

Another question:
Is it possible to use the 'Build log' to display messages generated by the pre-generate ?
This would be more consistent than display them in 'Code::Blocks log'.

Sincerely.
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 12, 2015, 07:19:16 pm
because actually I can use the context menu 'Build, Rebuild, Clean' with no break.
I doubt, because they have different ids, as far as I can see.
Have you tried to use them just after you've started a fresh instance of C::B?
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 12, 2015, 07:26:55 pm
I'll try because I am trying to compile svn 10116...
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 12, 2015, 07:35:55 pm
I confim...
I use svn 10116, rebuilt the plugin and context menus work correctly.
I'll check id's for safety ...
'QtPregenForCB' must be loaded after 'CompilerGcc',  but that's always the case !
I did a test by changing the name of the plugin 'CbqtPregen', and there the id's become -1!
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 12, 2015, 08:05:32 pm
I can believe you. There is no chance for this to work.
This is the code that registers the context menu items. Obviously the items don't reuse the ids from the main menu.
And I couldn't see any code that takes these ids.
Code: [Select]
        menu->Append(idMenuCompileFromProjectManager, _("Build"));
        menu->Append(idMenuRebuildFromProjectManager, _("Rebuild"));
        menu->Append(idMenuCleanFromProjectManager,   _("Clean"));

The dependence on the plugin load order is another nail in the coffin of this change!  8)
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 12, 2015, 08:13:55 pm
If you need to make a robust solution.
Take a look at the CompilerGCC::BuildStateManagement function. There is a switch for every build action.
You can invent an event that fires in this specific moment so it will always be correct.
You can add events that fire at the end of the action. So you will know when clean has started and also you'll know when it has finished. Also you'll know the same things about the other phases of the build.

Also there are the cbEVT_CLEAN_PROJECT_STARTED and cbEVT_CLEAN_WORKSPACE_STARTED events.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 12, 2015, 11:13:34 pm
I ask that you check, you'll see!

For
Code: [Select]
menu->Append(idMenuCompileFromProjectManager, _("Build"));
menu->Append(idMenuRebuildFromProjectManager, _("Rebuild"));
menu->Append(idMenuCleanFromProjectManager,   _("Clean"));

A little higher in the Dispatcher:

Code: [Select]
void CompilerGCC::Dispatcher(wxCommandEvent& event)
{
    m_EventId = event.GetId();
//    Manager::Get()->GetMessageManager()->Log(wxT("Dispatcher")));
    if (m_EventId == idMenuRun)
        OnRun(event);
    else if (m_EventId == idMenuCompileAndRun)
        OnCompileAndRun(event);
    else if (m_EventId == idMenuCompile)
        OnCompile(event);
    else if (m_EventId == idMenuCompileFromProjectManager)
        OnCompile(event);
    else if (m_EventId == idMenuCompileFile)
        OnCompileFile(event);
    else if (m_EventId == idMenuCompileFileFromProjectManager)
        OnCompileFile(event);
    else if (m_EventId == idMenuCleanFileFromProjectManager)
        OnCleanFile(event);
    else if (m_EventId == idMenuRebuild)
        OnRebuild(event);
    else if (m_EventId == idMenuRebuildFromProjectManager)
        OnRebuild(event);
....

we recover the same id's
Quote
idMenuCompileFromProjectManager
idMenuCleanFileFromProjectManager
idMenuRebuildFromProjectManager
triggers
Quote
OnCompile(event);
OnRebuild(event);

Quote
Take a look at the CompilerGCC::BuildStateManagement function.
I will try to understand how it works to use.
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 13, 2015, 12:10:03 am
I don't understand what you mean with the last post.
Do you agree that there is no chance for your plugin to work correctly when someone is using the context menu or are you seeing something in the code that I'm missing?

I ask that you check, you'll see!
I don't understand the meaning of this sentence.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 13, 2015, 09:20:55 am
I ask you to try the plugin 'QtPregenForCB' to verify that the context menu works correctly.
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 13, 2015, 09:40:22 am
Sorry, have no time to do it...
Title: Re: a new plugin : QtPregenForCB
Post by: MortenMacFly on February 14, 2015, 11:18:01 pm
Sorry, have no time to do it...
So you had no time but I had. Indeed, it works. I think you are wrong on that topic. And reverting a commit without proof that is does NOT work is not nice you know...  :(
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 14, 2015, 11:41:31 pm
Morten:
I've not reverted it because it doesn't work, but because it is bad design (this is a personal opinion/vision).
I would have reverted it even if I've tried it and it has worked.
Obviously we need to implement this feature as a new event that is fired at the correct time and it doesn't depend on a state variable.

p.s. Can you reason about why it works? How on earth the plugin matches correctly the id of the context menu items, when it has never requested them?
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 15, 2015, 09:04:54 am
@MortenMacFly
Thank you for taking the time to test this plugin.
Is it possible to use the 'Build log' to display messages generated by the pre-generate ?
This would be more consistent than display them in 'Code::Blocks log'.

@oBFusCATed
Quote
when it has never requested them
See 2-

1- It retrieves the ids menus created by the plugin 'CompilerGcc' by :
Code: [Select]
void QtPregen::BuildMenu(wxMenuBar* menuBar)
{
if (!IsAttached())
        return;

int pos = menuBar->FindMenu(_("Build"));
if (pos !=-1) {
wxMenu * builder = menuBar->GetMenu(pos);
m_IdBuild = builder->FindItem(_("Build"));
m_IdCompile = builder->FindItem(_("Compile current file"));
m_IdRun = builder->FindItem(_("Run"));
m_IdBuildRun = builder->FindItem(_("Build and run"));
m_IdRebuild = builder->FindItem(_("Rebuild"));
m_IdClean = builder->FindItem(_("Clean"));
}
}

2- It retrieves the ids context menus created by the plugin 'CompilerGcc' by :
Code: [Select]
void QtPregen::BuildModuleMenu(const ModuleType type, wxMenu* menu, const FileTreeData* data)
{
if (!IsAttached())
        return;

// we 're only interested in m_project manager's menus
    if (!menu || type != mtProjectManager)
        return;

// right click on item menu ...else -> 0
    if (data) {
    FileTreeData::FileTreeDataKind typedata  = data->GetKind();
    // ... click project
bool preproject = typedata == FileTreeData::ftdkProject  ;
// ... click file
bool prefile = typedata == FileTreeData::ftdkFile ;

if (preproject)  {
// popup menu on a project
m_IdpClean  = menu->FindItem(_("Clean"));
m_IdpBuild  = menu->FindItem(_("Build"));
m_IdpRebuild  = menu->FindItem(_("Rebuild"));
}
else
if (prefile) {
// popup menu on a file
m_IdfBuild  = menu->FindItem(_("Build file"));
m_IdfClean  = menu->FindItem(_("Clean file"));
}
      }
}

3- Id are used to select the treatment  in :
Code: [Select]
void QtPregen::OnPrebuild(CodeBlocksEvent& event)
{
      int eventId = event.GetId();
      ....
}
Note that from one session to another, id's remain the same!
While compiling a new version of svn 'Code::Block'.

Quote
Obviously we need to implement this feature as a new event that is fired at the correct time and it doesn't depend on a state variable.

Well, how so ?
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 15, 2015, 10:42:33 am
Hello,
- new 'QtPregenForCB-0.2.4'
- all private variables are prefixed with 'm_',
- improved user dialogs on error Qt utilities
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 15, 2015, 11:29:03 am
2- It retrieves the ids context menus created by the plugin 'CompilerGcc' by :
Code: [Select]
void QtPregen::BuildModuleMenu(const ModuleType type, wxMenu* menu, const FileTreeData* data)
{
if (!IsAttached())
        return;

// we 're only interested in m_project manager's menus
    if (!menu || type != mtProjectManager)
        return;

// right click on item menu ...else -> 0
    if (data) {
    FileTreeData::FileTreeDataKind typedata  = data->GetKind();
    // ... click project
bool preproject = typedata == FileTreeData::ftdkProject  ;
// ... click file
bool prefile = typedata == FileTreeData::ftdkFile ;

if (preproject)  {
// popup menu on a project
m_IdpClean  = menu->FindItem(_("Clean"));
m_IdpBuild  = menu->FindItem(_("Build"));
m_IdpRebuild  = menu->FindItem(_("Rebuild"));
}
else
if (prefile) {
// popup menu on a file
m_IdfBuild  = menu->FindItem(_("Build file"));
m_IdfClean  = menu->FindItem(_("Clean file"));
}
      }
}
What  a really clever hack. I'm stunned!


Quote
Obviously we need to implement this feature as a new event that is fired at the correct time and it doesn't depend on a state variable.

Well, how so ?
1. Create new event or even two events. One for starting and one for finishing.
2. Make an enum with all the possible types of actions you're interested in
3. Inspect the switch in CompilerGCC::BuildStateManagement and in every interesting case statement fire the appropriate event.
4. Test if all this is reliable... And doesn't slow the build process.
5. Probably it will be good if these events can be used to cancel the build process.
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 15, 2015, 11:40:32 am
Is it possible to use the 'Build log' to display messages generated by the pre-generate ?
This would be more consistent than display them in 'Code::Blocks log'.
I don't think there is a way.
Loggers have no name or id, so you cannot query them to obtain the index.
Only the one that has created them knows their index and can use them.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 15, 2015, 02:57:53 pm
@oBFusCATed
Quote
What  a really clever hack. I'm stunned!
Sir, is it a mockery or not ?
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 15, 2015, 05:04:21 pm
Hm. I don't think it is a mockery. I'm just amazed what you've done to solve your problem.  8)

p.s. Keep in mind that English is not my native language, so I may use the inappropriate words at times.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 15, 2015, 05:23:05 pm
Hello,
I would rather. I also use 'Google Translation' and that's why I asked for you. It's over.

Quote
3. Inspect the switch in CompilerGCC::BuildStateManagement and in every interesting case statement fire the appropriate event.
I do not know what to do ?
Regards
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 15, 2015, 07:57:31 pm
This is how you send and event:
Code: [Select]
        CodeBlocksEvent evt(<event type>, <parameters>);
        Manager::Get()->ProcessEvent(evt);

And you have to create one or more new events.
To see how to do it inspect the sdk_events.h/cpp files to see how the other events are declared/defined.
Copy/paste/modify the code until it fits you needs and post a patch.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 21, 2015, 07:15:25 pm
Hello,
- new 'QtPregenForCB-0.4.2'
- it uses a new organization for use of two new events:
Quote
'cbEVT_PRECOMPILER_STARTED' and
'cbEVT_PRECOMPILE_FILE'
I adapted 'CompilerGCC' to have a state machine with a state of more
Quote
bsTargetPreGen
see
Code: [Select]
'CompilerGCC::GetNextStateBasedOnJob()' and 'CompilerGCC::BuildStateManagement()'
I provide a patch to svn 10118, see to :
https://github.com/LETARTARE/QtPregenForCB (https://github.com/LETARTARE/QtPregenForCB)

Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 21, 2015, 07:56:27 pm
I hope you know that in the c++ world precompile and precompiled mean totally different things. So if these features stay, then you'll need to find better names.  Probably use a name similar to already use names like xxxxPreBuild.

Have you tried the solution I've proposed? What are its problems? Because the propose solution looks way more complex than it needs to be.

p.s. This struct "struct s_rebuild { bool workspace, clean, build; } ;" should be made public, if the code stays the same.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 21, 2015, 08:16:42 pm
Thank you for watching.
I suspected that the names will be to adapt. No problem, I look...
I used what you recommended, but to treat all cases, I arrived at this solution.
I can have a workspace with very different projects (Compilers, libraries ...), and it works.
I can use context menus('Build file', ...).

Quote
This struct "struct s_rebuild { bool workspace, clean, build; } ;" should be made public, if the code stays the same.
Of course, but I do not know where ?
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 21, 2015, 08:52:37 pm
I used what you recommended, but to treat all cases, I arrived at this solution.
What cases are not handled by my solution?
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 22, 2015, 01:49:40 pm
Hello,
-> new 'QtPregenForCB-0.5.0'

I deleted the state
Quote
bsTargetPreGen
I renamed the two events
Quote
'cbEVT_PREGEN_ALL' and
'cbEVT_PREGEN_FILE'
and methods
Quote
'void DoPreGenAll();'
'void DoPreGenFile(const wxString& file);'
The structure 's_rebuild' is declared public in' compilergcc.h '

I provide a new patch to svn 10118, see to :
https://github.com/LETARTARE/QtPregenForCB

Best regards

Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 22, 2015, 02:27:24 pm
compilergcc.h is not public. It is part of the compiler plugin and the CB's SDK.

Also you've not answer my last question.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 22, 2015, 02:34:05 pm
@oBFusCATed
I thought it was necessary to launch the event from a state machine.

's_prebuild' is used only in 'compilergcc.cpp' and 'qtPregen.cpp', Is not that enough?
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 22, 2015, 03:24:29 pm
@oBFusCATed
I thought it was necessary to launch the event from a state machine.
But why have you invented another state? Why do you need it?

's_prebuild' is used only in 'compilergcc.cpp' and 'qtPregen.cpp', Is not that enough?
qtPregen.cpp is part of your plugin and you're accessing headers that are part of another plugin, right?
Do you think this is correct? What will happen if I want to use this event in another plugin and don't have the full source tree of codeblocks, but I'm using the headers installed in /usr/include/codeblocks?

The public SDK is comprised of the files in src/include and libcodeblocks.so anything that is not part of these two should not be used by a plugin!
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 22, 2015, 03:40:23 pm
@oBFusCATed
Quote
The public SDK is comprised of the files in src/include and libcodeblocks.so anything that is not part of these two should not be used by a plugin!

do 'cbplugin.h' correct ?
Title: ...
Post by: oBFusCATed on February 22, 2015, 03:44:16 pm
Nope. Place it next to the corresponding event. In sdk_events.h or similar header.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 22, 2015, 05:03:28 pm
Hello,
-> new 'QtPregenForCB-0.6.0'

Quote
In sdk_events.h or similar header
The structure 's_rebuild' is declared public in 'sdk_events.h'.

I provide a new patch to svn 10118, see to :
https://github.com/LETARTARE/QtPregenForCB

Sincerely
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 22, 2015, 06:37:13 pm
OK, some more comments:
1. Why don't you use an enum instead of s_rebuild struct? An enum has the advantage that it can be extended without the need to break the api/abi.
2. The names of the events continue to be horrible. I don't know what PREGEN should mean. It has a meaning in the context of your plugin, but not as a generic event emitted by the compiler plugin.
3. Check the style guide here http://wiki.codeblocks.org/index.php?title=Coding_style and try to follow it.
4. Don't put LETARTARE everywhere. It would be removed before committing anyway.
5. Are you sure that you want to get an event when the pre-build step is executed?

@devs:
What do you think about adding an event like cbEVT_COMPILER_STEPS_STARTED?
This event will be emitted before every different step (clean, build, pre, post build, etc).
Would this make building too slow?
Also please take a look at this patch, because I have very little understanding of the compiler plugin.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 23, 2015, 04:50:30 pm
@ofuscated
Quote
1-  Why don't you use an enum instead of s_rebuild struct
yes it's possible, as I used three boolean, I have to use eight enums par exemple :
Code: [Select]
enum cbFutureBuild
{
    fbNone = 0,
    fbBuild,
    fbClean,
    fbRebuild,
    fbWorkspaceBuild,
    fbWorkspaceClean,
    fbWorkspaceReBuild
};
Quote
2-The names of the events continue to be horrible
you are right : names must remember that this happens BEFORE COMPILATION
Quote
'cbEVT_BEFORE_COMPILING_ALL'
'cbEVT_BEFORE_COMPILING_FILE'
??
Quote
3-Check the style guide
is corrected
Quote
4-Don't put LETARTARE everywhere
this is done
Quote
5-  Are you sure that you want to get an event
yes, i have to generate the files required by Qt structure, BEFORE the compilation starts : see green
http://doc.qt.digia.com/qq/34/qt-build-system.png (http://doc.qt.digia.com/qq/34/qt-build-system.png)
But I will try to use 'cbEVT_COMPILER_STARTED' instead of 'cbEVT_BEFORE_COMPILING_ALL'

I will provide the patch if you agree ?

Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 24, 2015, 10:45:35 am
Hello,
-> new 'QtPregenForCB-0.7.1'

This version uses only event 'cbEVT_COMPILER_STARTED' associated with the relevant parameter.
The 'enum cbFutureBuild' replaces 'struct s_rebuild'.

I provide a new patch to svn10118, see to :
https://github.com/LETARTARE/QtPregenForCB

Sincerely

modification of the patch: error version !!
Title: Re: a new plugin : QtPregenForCB
Post by: oBFusCATed on February 24, 2015, 02:29:57 pm
Hm, am I correct in thinking that know the compiler plugin will fire cbEVT_COMPILER_STARTED event twice for two separate reasons?
One at the beginning of the build and another for every project/target it starts to build.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 24, 2015, 03:14:13 pm
Yes,
One at the beginning of the worspace/project/target build and another for build one file, because the parameters are different.
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on February 27, 2015, 08:51:56 pm
Hello,
-> new 'QtPregenForCB-0.8.3'

I created a log 'PreBuild log' in log manager for posts plugin see
http://forums.codeblocks.org/index.php/topic,20045.msg136838.html#msg136838 (http://forums.codeblocks.org/index.php/topic,20045.msg136838.html#msg136838)

I provide a patch to svn10118, svn10127 see to :
https://github.com/LETARTARE/QtPregenForCB

@devs
This patch is not specific to Qt, it can be used for any intervention BEFORE building
1- workspace
2- project
3- targets
4- a simple file

Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on April 13, 2015, 04:26:43 pm
Hello,
a new patch to svn10216, see to :
https://github.com/LETARTARE/QtPregenForCB (https://github.com/LETARTARE/QtPregenForCB)
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on October 17, 2015, 08:37:59 pm
a new version 'QtPregenForCB-0.8.5' for sdk >= 1.25.
new patchs to  svn10253, svn10376, svn10474, svn10528, see to :
https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on November 23, 2015, 06:39:58 pm
- patch for cb-svn10600
- use of version 0.8.5 with cb-svn10600
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on January 27, 2016, 06:05:42 pm
- patch for cb-svn10703
- use of version 0.8.5 with cb-svn10703
https://github.com/LETARTARE/QtPregenForCB (https://github.com/LETARTARE/QtPregenForCB)
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on January 29, 2016, 07:50:15 pm
- patch for cb-16.01
- use of version 0.8.5 with cb-16.01
https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on March 23, 2016, 12:10:36 am
- patch for svn10816
- use of version 0.8.5 with svn10816
https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on November 22, 2016, 07:41:07 pm
- patch for svn10922
- use of version 0.8.6 with svn10922
https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on March 05, 2017, 08:54:41 pm
- patch for svn11021
- use of version 0.8.6 with svn11021
https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on August 04, 2017, 10:05:51 am
- patch for svn11112
- use of version 0.9.0 with svn11112

Quote
Improvements :
- when activating a Qt project : detection of existing complement files,
- when cleaning a Qt project : deleting complement files to disk,
- new documentation,

https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on October 16, 2017, 03:59:14 pm
- patch for svn11176
- use of version 0.9.0 with svn11176, sdk 1.31.0
https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a new plugin : QtPregenForCB
Post by: LETARTARE on October 21, 2017, 01:03:39 am
- patch for svn11210
- use of version 0.9.0 with svn11210, sdk 1.32.0
https://github.com/LETARTARE/QtPregenForCB
Best regards
Title: Re: a plugin : QtPregen
Post by: LETARTARE on December 09, 2017, 07:28:11 pm
- patch for svn11246
- use of version 1.0 with svn11246, sdk 1.33.0
https://github.com/LETARTARE/QtPregen (https://github.com/LETARTARE/QtPregen)

A Linux-64 version is under study ...

Best regards
Title: Re: a plugin : QtPregen for C::B
Post by: LETARTARE on December 19, 2017, 03:44:36 pm
=> New version 1.1.0
- new algorithm for recording complementary files,
- thanks to @Pecan : see http://forums.codeblocks.org/index.php/topic,22320.0.html (http://forums.codeblocks.org/index.php/topic,22320.0.html)
      =>  fix project detection Qt for newly created projects,
- patch for svn11246

- use of version 1.1 with svn11246, sdk 1.33.0
https://github.com/LETARTARE/QtPregen

Best regards
Title: Re: a plugin : QtPregenForCB
Post by: LETARTARE on August 28, 2018, 11:46:50 pm
=> New version 2.3.0 (Win-32 and Linux-64)

- For Linux-64 the tests concern Opensuse-Leap-42.3 with wx28 and Gcc-4.8.5.

- Patch for svn11454

- Use of version 2.3.0 with svn11454, sdk 1.36.0
https://github.com/LETARTARE/QtPregen
Title: Re: a plugin : QtPregenForCB
Post by: LETARTARE on December 21, 2018, 05:39:51 pm
=> New version 2.4.0 (Win-32 and Linux-64)

- Complete redesign of the deletion of creative and additional files.

- For Linux-64 the tests concern Opensuse-Leap-42.3 with wx28 and Gcc-4.8.5.

- Patch for svn11530

- Use of version 2.4.0 with svn11530, sdk 1.36.0
https://github.com/LETARTARE/QtPregen