CoApp Client Engine

Gnome app stack needs packaging

Asked by Dimitri John Ledkov

I dream of a day when the whole Gtk+/Gnome stack can be easily deployed in msi components such that I don't have to have a bundled copy of libs in each Gnome app i want to run on Windows e.g. evince & gedit.

Gnome needs packaging using this thing when it's done =)

Congrats on the first bug? =)

Question information

Language:
English Edit question
Status:
Solved
For:
CoApp Client Engine Edit question
Assignee:
No assignee Edit question
Solved by:
Dimitri John Ledkov
Solved:
Last query:
Last reply:

This question was originally filed as bug #560362.

Revision history for this message
Garrett Serack (garretts) said : 		#1

That's kind of the idea.

However, I'd probably classify this as "feature request" rather than "bug".

Congrats. :p

Revision history for this message
Garrett Serack (garretts) said : 		#2

This is a feature request, not a bug.

Revision history for this message
Garrett Serack (garretts) said : 		#3

Hmm.

Just for completion sake, can you articulate what all the dependencies are (static or dynamic) to satisfy this type of thing.

Perhaps the example data for this could be constructive in ensuring we don't miss something (design-wise).

G

Revision history for this message
Jernej Simončič (jernej+s-launchpad) said : 		#4

For the dependencies, you could look at the SuSE build server, which provides Windows binaries compiled with mingw:
http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_11.2/noarch/

Revision history for this message
Dimitri John Ledkov (xnox) said : 		#5

Jernej Simončič thanks I'm already using that =) but i wasn't quite happy with those so I'm making a jhbuild modulest to create a different toolchain. Hopefully will start publishing soon on launchpad and then later on the opensuse buildservice.

=) but it would be greate to be able to cross-compile CoApp binaries & publish repositories.

Closing for now as I will keep an eye on CoApp =)