News:

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

Main Menu

Why wxSmith is dependency for other plugins?

Started by oBFusCATed, October 03, 2011, 11:20:16 AM

Previous topic - Next topic

oBFusCATed

Why are we building the wxsmith plugins as dependency for other plugins (ThreadSearch, libfinder, etc)?

I'm having problems compiling the wxsmith on Fedora8+wxGTK 2.8.9 and I've tried to disable all wxSmith plugins.
Unfortunately the plugin is still built.

Probably we should fail the configure step if wxSmith is disabled and ThreadSearch/libfinder is enabled.
Jens, what do you think on this matter?
(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!]

ollydbg

I just look at the dependency on threadsearch plugin in ContribPlugins.workspace, I found that it depend on wxCustombutton, and wxCustombutton is include in wxSmithContribItems project.
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.

Jenna

Quote from: ollydbg on October 03, 2011, 11:40:25 AM
I just look at the dependency on threadsearch plugin in ContribPlugins.workspace, I found that it depend on wxCustombutton, and wxCustombutton is include in wxSmithContribItems project.
And that needs wxSmith.
That's the cause for the dependency.
And similar for libfinder: it uses wxFlatNotebook.

Both automatically select wxSmith and wxSmithContribItems to build in automake-system.

oBFusCATed

OK, as we know the problem how would we fix it?
Probably fixing configure is the first step, but this situation looks like wrong setup of dependencies.
As long term, correct solution, we should move the wx-related-libs in the src/plugins/contrib/wxlibs (or something similar).
And then the dependencies will be correct and logical.
What do you think?

(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!]

Jenna

Quote from: oBFusCATed on October 03, 2011, 12:20:19 PM
As long term, correct solution, we should move the wx-related-libs in the src/plugins/contrib/wxlibs (or something similar).
And then the dependencies will be correct and logical.
What do you think?
Moving all contrib-items into a seperate project and use it as dependency for wxSmithConribItems, would be the best solution in my opinion.
Not only as long term solution, but also as short term solution.

I can do it this week (no work) and fix all related projects, if no other devs have objections against it.

We should do the same (or similar) for all new items in the wxSmith-branch, too.

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!]

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!]

MortenMacFly

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]

Jenna

I did it for trunk on linux (project-files and automake), seems to work.
I hope I find the time to do it for windows this evening or tomorrow.
The new project is called wxContribItems and builds wxFlatNotebook, wxChartCtrl and wxCustomButton.

Jenna

The changes are committed to the wxsmith-branch.
More of them (for the new items in this branch) will follow.