On Thursday 20 March 2008, Marcel Partap wrote:
> Then run wine with
> LD_LIBRARY_PATH=/pathtoyourwinetree/libs /pathtoyourwinetree/wine
> something.exe...
I'm pretty sure you don't need to set LD_LIBRARY_PATH there, at least I've
never needed to (and the wine script appears to do that).
- Neil
> Can you be more specific on what the issues are here? Just curious.
Well.. basically everything that goes beyond compiling small one-file programs
not using the win32api :)
I have to add that i didn't start hacking wine as first step but built an exe
file outside of wine,
so everything that i
I think he's a windows developer, comfortable mostly
with IDEs like Visual C++. He'd like to build winecfg
as a .exe on Wine, test it there, and also try running
it on Windows (at least part of it should kinda work there).
Here's what I told him:
On Ubuntu, 'sudo apt-get install mingw' should in
Am Donnerstag, 20. März 2008 16:05:51 schrieb [EMAIL PROTECTED]:
> Question 1: I need to mess about with winecfg. I want to compile only
> winecfg.exe so I can immediately see when I made a mistake /rather than
> trying to build the entire source of wine/. What's the console command(s) I
> need to
On Thu, Mar 20, 2008 at 9:13 AM, Marcel Partap <[EMAIL PROTECTED]> wrote:
> > but it seems I didn't quite understand the rules of
> > the dev on wine/ or on linux for that matter :(
> > I need someone to show me the ropes...
> > Basically, The Toolbox.
> Last year THAT was my biggest initial p
> but it seems I didn't quite understand the rules of
> the dev on wine/ or on linux for that matter :(
> I need someone to show me the ropes...
> Basically, The Toolbox.
Last year THAT was my biggest initial problem as well. There are really a few
caveats you will most
probably hit (seems to m
