Re: [wxhaskell-users] wxHaskell modularity

[shelarcy <she...@gm...>]

Hi Jeremy,

On Mon, 20 Aug 2007 23:48:38 +0900, Jeremy O'Donoghue <jer...@gm...> wrote:
> 1) Build wxC wrapper for wxWidgets. Building this is really quite
> dependent on how
>    wxWidgets itself was built, which is OK on Unix (wx-config tells
> you), but subject
>    to much pain and guesswork on Windows.
>    STC support is built at this time. If STC is not present in the
> wxWidgets build,
>    the wxSTC functions are all empty (but present).

I think we can solve this problem by modifying wxc-*.dsw.
If we write "Project Dependency" on dsw file, Visual C++ build
dependency before build wxc.
(But we must use "Unicode **" instead of "**". See attached
wxcu-2.6.4.dsw and doc-fix.dpatch.)

It look fine for me, so I planed to remove --with-contrib and
requiring to install contrib library as 2. option in this thread.

http://thread.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/199/focus=249


The problem is that we can't use nmake, because building on Windows
deeply depends on Visual C++ project files.

But we can generate Visual C++ project (.dsp) file instead of make.nmake.
I also attached GenVCProject.hs that is Visual C++ project file generator.
(That code is messy now, but we can refactor it. And It is easier to
modifying .dsp file by using that.)


> (note
> that this would probably preclude Linux users from using the wxWidgets
> provided by their package manager as the chances would be pretty high
> that it would be incorrectly configured).

I have a question about that, so I send previous mail.


Best Regards,

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/