※ 下記のＵＲＬからご確認出来ます。
http://www.10wn.com/h/?bank38
▼ 三智子さま
▼ 橋本 ゆうこ
２名の女性の方から、謝礼の提示がありました。
┌───
│ 配信停止はコチラまで。
│ DeliveryStop
│ [EMAIL PROTECTED]
│
│【配信停止手続きの際は】
│必ず件名に「配信停止」とお書き下さい。
│件名に「配信停止」と記載されていない場合は処理が行えません。
│尚、停止に
Hi Eric,
On 21/08/07, Eric Kow <[EMAIL PROTECTED]> wrote:
> Hi Jeremy,
>
> > (*) There's a secondary reason for factoring out the wxc build from
> > the wxHaskell build: a number of other languages (most of them in the
> > FP church, if you define it reasonably broadly) use wxC as the basis
> > fo
Hi Shelarcy,
On 20/08/07, shelarcy <[EMAIL PROTECTED]> wrote:
>
> On Tue, 21 Aug 2007 00:42:26 +0900, Jeremy O'Donoghue <[EMAIL PROTECTED]>
> wrote:
> >
> > This really only works as an option if we decide that users must build
> > wxWidgets from source *before* they can build wxHaskell.
>
> Real
Hi Jeremy,
> (*) There's a secondary reason for factoring out the wxc build from
> the wxHaskell build: a number of other languages (most of them in the
> FP church, if you define it reasonably broadly) use wxC as the basis
> for their wxWidgets bindings.
Are you aware of the wxc project by any c
HI Shelarcy,
On 21/08/07, shelarcy <[EMAIL PROTECTED]> wrote:
>
> The problem is that we can't use nmake, because building on Windows
> deeply depends on Visual C++ project files.
I've actually already almost solved this.
I've factored out the wxc build from the top level makefile(*) and
made it
