JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* faq-programming.xml (faq.programming.unix-gui): Update to

Browse Source 
reflect the availability of X11 toolkits on Cygwin.
This commit is contained in:
Yaakov Selkowitz 2012-07-18 02:11:04 +00:00
parent 392c090c7e
commit 03b7882aa0
2 changed files with 43 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2012-07-17 Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
* faq-programming.xml (faq.programming.unix-gui): Update to
reflect the availability of X11 toolkits on Cygwin.
2012-06-03 Corinna Vinschen <corinna@vinschen.de> 2012-06-03 Corinna Vinschen <corinna@vinschen.de>
* new-features.sgml (ov-new1.7.16): Document ReFS support. * new-features.sgml (ov-new1.7.16): Document ReFS support.

52
winsup/doc/faq-programming.xml
View File

@ -810,20 +810,44 @@ a Windows environment which Cygwin handles automatically.
<question><para>How should I port my Unix GUI to Windows?</para></question> <question><para>How should I port my Unix GUI to Windows?</para></question>
<answer> <answer>
<para>There are two basic strategies for porting Unix GUIs to Windows. <para>Like other Unix-like platforms, the Cygwin distribtion includes many of
</para> the common GUI toolkits, including X11, X Athena widgets, Motif, Tk, GTK+,
<para>The first is to use a portable graphics library such as tcl/tk, X11, or and Qt. Many programs which rely on these toolkits will work with little, if
V (and others?). Typically, you will end up with a GUI on Windows that any, porting work if they are otherwise portable. However, there are a few
requires some runtime support. With tcl/tk, you'll want to include the things to look out for:</para>
necessary library files and the tcl/tk DLLs. In the case of X11, you'll <orderedlist>
need everyone using your program to have the X11 server installed. <listitem><para>Some packages written for both Windows and X11 incorrectly
</para> treat Cygwin as a Windows platform rather than a Unix variant. Mixing Cygwin's
<para>The second method is to rewrite your GUI using Win32 API calls (or MFC Unix APIs with Windows' GDI is best avoided; rather, remove these assumptions
with VC++). If your program is written in a fairly modular fashion, you so that Cygwin is treated like other X11 platforms.</para></listitem>
may still want to use Cygwin if your program contains a lot of shared <listitem><para>GTK+ programs which use <literal>gtk_builder_connect_signals()</literal>
(non-GUI-related) code. That way you still gain some of the portability or <literal>glade_xml_signal_autoconnect()</literal> need to be able to
advantages inherent in using Cygwin. <literal>dlopen()</literal> themselves. In order for this to work, the program
</para> must be linked with the <literal>-Wl,--export-all-symbols</literal> linker flag.
This can be added to LDFLAGS manually, or handled automatically with the
<literal>-export-dynamic</literal> libtool flag (requires libtool 2.2.8) or
by adding <literal>gmodule-export-2.0</literal> to the pkg-config modules used
to build the package.</para></listitem>
<listitem><para>Programs which include their own loadable modules (plugins)
often must have its modules linked against the symbols in the program. The
most portable solution is for such programs to provide all its symbols (except
for <literal>main()</literal>) in a shared library, against which the plugins
can be linked. Otherwise, the symbols from the executable itself must be
exported.</para>
<para>If the package uses the CMake build system, this can be done by adding
<literal>ENABLE_EXPORTS TRUE</literal> to the executable's <literal>set_target_properties</literal>
command, then adding the executable's target name to the <literal>target_link_libraries</literal>
command for the plugins.</para>
<para>For other build systems, the following steps are required:</para>
<orderedlist>
<listitem><para>The executable must be built before its plugins.</para></listitem>
<listitem><para>Symbols must be exported from the executable with a
<literal>-Wl,--export-all-symbols,--out-implib,libfoo.exe.a</literal>
linker flag, where <literal>foo</literal> represents the name of the
executable.</para></listitem>
<listitem><para>The plugins must be linked with a <literal>-Wl,/path/to/libfoo.exe.a</literal>
linker flag.</para></listitem>
</orderedlist></listitem></orderedlist>
</answer></qandaentry> </answer></qandaentry>
<qandaentry id="faq.programming.djgpp"> <qandaentry id="faq.programming.djgpp">