From: Cesar Eduardo Barros <cesarb@cesarb•net>
To: Junio C Hamano <gitster@pobox•com>
Cc: msysgit@googlegroups•com,
Johannes Schindelin <Johannes.Schindelin@gmx•de>,
git@vger•kernel.org
Subject: Re: [PATCH v2] Embed an application manifest on MinGW
Date: Thu, 02 Jun 2011 19:56:47 -0300 [thread overview]
Message-ID: <4DE8152F.3010903@cesarb.net> (raw)
In-Reply-To: <7vfwnsdwqf.fsf@alter.siamese.dyndns.org>
Em 02-06-2011 13:27, Junio C Hamano escreveu:
> Does the output from $WINDRES define any external symbol the rest of the
> code can refer to? If so, you could throw resource.o into one of the .a
> file and make sure that the symbol is referred to from main(); perhaps the
> definition of main in compat/mingw.h can refer to it.
Unfortunately no:
$ i686-pc-mingw32-nm compat/win32/resource.o
00000000 d .rsrc
The only thing it has is the .rsrc section.
I could perhaps create a dummy C file with a dummy variable, compile it,
and use incremental linking (ld -r) to bolt both object files together.
I am not sure this hack wouldn't be uglier than the Makefile changes.
Another possibility would be a linker script (like /usr/lib/libc.so on
modern distributions). This might be the most elegant option if it
works. I will have to take a look on how it works to see if it is a
viable alternative.
> If you can do that, you wouldn't need any change to the Makefile other
> than the rule to build compat/win32/resource.o and conditionally add that
> object to LIB_OBJS, perhaps like this (obviously untested as I do not have
> access to windows boxes).
You do not need access to Windows boxes, you can always use Wine ;-)
(msysgit even has a script to open a shell under Wine with everything
set up).
--
Cesar Eduardo Barros
cesarb@cesarb•net
cesar.barros@gmail•com
prev parent reply other threads:[~2011-06-02 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 10:35 [PATCH v2] Embed an application manifest on MinGW Cesar Eduardo Barros
2011-06-02 14:26 ` Johannes Schindelin
2011-06-02 16:27 ` Junio C Hamano
2011-06-02 22:56 ` Cesar Eduardo Barros [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE8152F.3010903@cesarb.net \
--to=cesarb@cesarb$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=msysgit@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox