Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: oBFusCATed on October 03, 2011, 11:20:16 am

Title: Why wxSmith is dependency for other plugins?
Post by: oBFusCATed on October 03, 2011, 11:20:16 am

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?

Title: Re: Why wxSmith is dependency for other plugins?
Post by: 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.

Title: Re: Why wxSmith is dependency for other plugins?
Post by: Jenna on October 03, 2011, 11:53:20 am

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.

Title: Re: Why wxSmith is dependency for other plugins?
Post by: oBFusCATed on October 03, 2011, 12:20:19 pm

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?

Title: Re: Why wxSmith is dependency for other plugins?
Post by: Jenna on October 03, 2011, 02:16:05 pm

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.

Title: Re: Why wxSmith is dependency for other plugins?
Post by: oBFusCATed on October 03, 2011, 02:40:28 pm

No objections  :lol:

Title: Re: Why wxSmith is dependency for other plugins?
Post by: oBFusCATed on October 03, 2011, 02:45:34 pm

BTW: any objections against committing this patch: http://smrt.is-a-geek.org/codeblocks/patches/wx289.patch

Title: Re: Why wxSmith is dependency for other plugins?
Post by: MortenMacFly on October 06, 2011, 07:22:01 am

Quote from: oBFusCATed on October 03, 2011, 02:45:34 pm

BTW: any objections against committing this patch: http://smrt.is-a-geek.org/codeblocks/patches/wx289.patch

If it works, no. ;-)

Title: Re: Why wxSmith is dependency for other plugins?
Post by: Jenna on October 06, 2011, 05:32:17 pm

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.

Title: Re: Why wxSmith is dependency for other plugins?
Post by: Jenna on November 06, 2011, 10:38:18 am

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