Martin Dulovits | 1 Sep 14:10
Picon
Favicon

Working Solution for x64 windows build

Did somebody succeed in building openexr and iex for x64 windows ?
Can anyone post a working solution or a patched createdll.cpp ?
I just get thousands of unresolved symbols no matter if i use msvc or icc.

thx Dulo
Ger Hobbelt | 1 Sep 22:03
Favicon
Gravatar

Re: Working Solution for x64 windows build

Got an MSVC2005 build for x64 and IA64; warning: lightly tested!
(CreateDLL has seen several changes, but here also: think of this as
beta quality today -- I mentioned I was working on this on the list a
few months ago and that I would post the 'updated' CreateDLL when
stabalized; it's getting close...)

If you don't mind leaking edge source code, I can put an archive of
the stuff up on my site by tomorrow, so you can have a look if you
like?

(FYI: the stuff has just entered the preliminary initial (small scale)
field test overhere, so expect bugs, okay?)

Ger

On Mon, Sep 1, 2008 at 2:10 PM, Martin Dulovits
<martin.dulovits <at> woogieworks.at> wrote:
> Did somebody succeed in building openexr and iex for x64 windows ?
> Can anyone post a working solution or a patched createdll.cpp ?
> I just get thousands of unresolved symbols no matter if i use msvc or icc.
>
> thx Dulo
>
>
>
> _______________________________________________
> Openexr-devel mailing list
> Openexr-devel <at> nongnu.org
> http://lists.nongnu.org/mailman/listinfo/openexr-devel
>
(Continue reading)

Ger Hobbelt | 2 Sep 01:54
Favicon
Gravatar

Re: Working Solution for x64 windows build

Okay, Martin.

There's some stuff on-line at http://hebbut.net/ now. Look for the
OpenEXR link, go there and download both the OpenEXR and zlib 7zip
archives (20080901). (If you don't have 7zip yet, see www.7zip.org --
I use it for all my stuff as my bandwidth is limited and less bytes ==
faster download ;-) )

Sourcecode is synced to todays CVS, but has some minor patches in
there. Diff to CVS to see what I did. CreateDLL has seen bigger
changes though: the tables and code has been adapted to handle
MSVC2005 Win32/Win64 targets x86/x86_64 and IA64. Commandline
interface changed to allow for arbitrary platform flags for MS linker,
so you may even be able to use this bugger for targeting ARM or other
now, but that comes UNTESTED. ;-)

I just plonked the whole dev tree in there minus intermediates so
you'll get both sources and debug+release binaries as I have them (ran
a batchbuild to make sure everything is in there and at least
_possibly_ okay too).

Note that the projects use Win32-based CreateDLL tool build as I
develop and cross-compile on a Win32 XP system (yeah, I know, but the
big iron is reserved for another purpose and that software doesn't
like development packages on the same box - besides I lack IA64
hardware here so when you've got such a box, YMMV).

Anyway, when you fetch both archives and 'extract here' in the same
directory, the solution as described on the OpenEXR page I whipped up
should compile/rebuild all without yakking about zlib as it should
(Continue reading)

Ger Hobbelt | 3 Sep 05:06
Favicon
Gravatar

Re: Working Solution for x64 windows build

Nick, please be aware that Martin still has an issue with it, but I
think his last message about that was off list, so I would suggest you
hold for a bit until that bug gets cleared.

Ger

snippet from Martin's:

--------------------------------------------------------------
Error    1     error LNK2019: unresolved external symbol "private:
static unsigned short const * const half::_eLut" (?_eLut <at> half@@0QBGB)
referenced in function "public: __cdecl half::half(float)"
(??0half@@QEAA <at> M@Z)    bf_openexr.lib(openexr_api.obj)
--------------------------------------------------------------

On Wed, Sep 3, 2008 at 2:51 AM, Nick Porcino <nporcino <at> ilm.com> wrote:
> Thanks Ger, I'll have a look at your version in the next little while.
>
> If anyone has run the IA64 build on IA64 hardware, I'd love to know the results.
>
> -----Original Message-----
> From: openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org
[mailto:openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org] On Behalf Of Ger Hobbelt
> Sent: Monday, September 01, 2008 4:54 PM
> To: Martin Dulovits
> Cc: openexr-devel <at> nongnu.org
> Subject: Re: [Openexr-devel] Working Solution for x64 windows build
>
> Okay, Martin.
>
(Continue reading)

Ger Hobbelt | 3 Sep 18:07
Favicon
Gravatar

Re: Working Solution for x64 windows build

Nick,

Martin reported back and his trouble has been resolved. Unfortunately
for CreateDLL, he's using static libs, so that would mean CreateDLL
isn't coming into play, at least if I understand it correctly. _that_
means theoretically there still might may be a lingering issue with
"private: static unsigned short const * const half::_eLut" (?_eLut <at> half@@0QBGB)"
which I haven't seen happen on my systems yet, so if there's anyone
out there who likes to try and build the stuff in DLL mode with apps
other than the samples available with the OpenEXR lib, just to
doublecheck that I did not screw up some exports in any way, it's much
appreciated.

Meanwhile, Nick, if you like to take a look, by all means. The OpenEXR
archive will remain on-line, so you can get it anytime you like, no
hurry.

Thanks,

Ger

On Wed, Sep 3, 2008 at 2:51 AM, Nick Porcino <nporcino <at> ilm.com> wrote:
> Thanks Ger, I'll have a look at your version in the next little while.
>
> If anyone has run the IA64 build on IA64 hardware, I'd love to know the results.
[...]
> There's some stuff on-line at http://hebbut.net/ now. Look for the
> OpenEXR link, go there and download both the OpenEXR and zlib 7zip
> archives (20080901). (If you don't have 7zip yet, see www.7zip.org --

(Continue reading)

Josef Grunig | 11 Sep 14:52
Picon
Gravatar

Re: Working Solution for x64 windows build

Very interesting, great contribution.

Do you have also a project configuration for static lib?
Would be very appreciated!

Josef Grunig

On Mon, Sep 1, 2008 at 10:03 PM, Ger Hobbelt <ger <at> hobbelt.com> wrote:
> Got an MSVC2005 build for x64 and IA64; warning: lightly tested!
> (CreateDLL has seen several changes, but here also: think of this as
> beta quality today -- I mentioned I was working on this on the list a
> few months ago and that I would post the 'updated' CreateDLL when
> stabalized; it's getting close...)
>
> If you don't mind leaking edge source code, I can put an archive of
> the stuff up on my site by tomorrow, so you can have a look if you
> like?
>
> (FYI: the stuff has just entered the preliminary initial (small scale)
> field test overhere, so expect bugs, okay?)
>
> Ger
>
>
> On Mon, Sep 1, 2008 at 2:10 PM, Martin Dulovits
> <martin.dulovits <at> woogieworks.at> wrote:
>> Did somebody succeed in building openexr and iex for x64 windows ?
>> Can anyone post a working solution or a patched createdll.cpp ?
>> I just get thousands of unresolved symbols no matter if i use msvc or icc.
>>
(Continue reading)

Ger Hobbelt | 11 Sep 17:58
Favicon
Gravatar

Re: Working Solution for x64 windows build

Erm, not really, but I can see what I can do regarding that. Isn't
that hard to do really - it just takes time.

Basic trick would be along these lines: get the vcproj files for the
DLLs in a text editor; kill the GUIDs at the top (as you are creating
different projects) and change the type code (a number) to the number
you see appearing in any static lib vcproj, then same as different
filenames. The .sln will be blown to smithereens then, so you'll have
to setup build dependencies between libs from scratch. Oh, And the
post-build lines calling the createDLL tool have to be removed from
the vcproj files as well.

After that, it's a few rounds of building the stuff and checking all
the compiler and linker settings (including preprocessor symbols) and
making sure that the test apps actually run.

Anyway, I'll see what I can do, but don't expect a result this week -
too busy with other stuff - hence the above short description how to
tackle this on your own if the need is urgent.

Ger

On Thu, Sep 11, 2008 at 2:52 PM, Josef Grunig <josef.grunig <at> gmail.com> wrote:
> Very interesting, great contribution.
>
> Do you have also a project configuration for static lib?
> Would be very appreciated!
>
> Josef Grunig
>
(Continue reading)

Piotr Stanczyk | 11 Sep 18:19
Gravatar

Re: Working Solution for x64 windows build

Thanks for that Ger,

Nick and I will try to get this into the next release all being well.

Piotr

Ger Hobbelt wrote:
> Erm, not really, but I can see what I can do regarding that. Isn't
> that hard to do really - it just takes time.
>
> Basic trick would be along these lines: get the vcproj files for the
> DLLs in a text editor; kill the GUIDs at the top (as you are creating
> different projects) and change the type code (a number) to the number
> you see appearing in any static lib vcproj, then same as different
> filenames. The .sln will be blown to smithereens then, so you'll have
> to setup build dependencies between libs from scratch. Oh, And the
> post-build lines calling the createDLL tool have to be removed from
> the vcproj files as well.
>
> After that, it's a few rounds of building the stuff and checking all
> the compiler and linker settings (including preprocessor symbols) and
> making sure that the test apps actually run.
>
>
>
> Anyway, I'll see what I can do, but don't expect a result this week -
> too busy with other stuff - hence the above short description how to
> tackle this on your own if the need is urgent.
>
> Ger
(Continue reading)

Josef Grunig | 12 Sep 10:28
Picon
Gravatar

Re: Working Solution for x64 windows build

Thank you Ger,

I created a new "Release_Static" configuration in VS and changed
settings accordingly.
Finally I linked the stuff manually together... Hope it works...

thanks for the hints...

Josef Grunig

On Thu, Sep 11, 2008 at 5:58 PM, Ger Hobbelt <ger <at> hobbelt.com> wrote:
> Erm, not really, but I can see what I can do regarding that. Isn't
> that hard to do really - it just takes time.
>
> Basic trick would be along these lines: get the vcproj files for the
> DLLs in a text editor; kill the GUIDs at the top (as you are creating
> different projects) and change the type code (a number) to the number
> you see appearing in any static lib vcproj, then same as different
> filenames. The .sln will be blown to smithereens then, so you'll have
> to setup build dependencies between libs from scratch. Oh, And the
> post-build lines calling the createDLL tool have to be removed from
> the vcproj files as well.
>
> After that, it's a few rounds of building the stuff and checking all
> the compiler and linker settings (including preprocessor symbols) and
> making sure that the test apps actually run.
>
>
>
> Anyway, I'll see what I can do, but don't expect a result this week -
(Continue reading)

Ger Hobbelt | 12 Sep 13:41
Favicon
Gravatar

Re: Working Solution for x64 windows build

On Fri, Sep 12, 2008 at 10:28 AM, Josef Grunig <josef.grunig <at> gmail.com> wrote:
> Thank you Ger,
>
> I created a new "Release_Static" configuration in VS and changed
> settings accordingly.
> Finally I linked the stuff manually together... Hope it works...
>
> thanks for the hints...

You're welcome. ;-)

(If the binary acts up, first thing I do in these cases is check all
the /D preprocessor defines to ensure those are okay for a static lib
build. Just in case...)

Take care,

Ger

--

-- 
Met vriendelijke groeten / Best regards,

Ger Hobbelt

--------------------------------------------------
web: http://www.hobbelt.com/
 http://www.hebbut.net/
mail: ger <at> hobbelt.com
mobile: +31-6-11 120 978
--------------------------------------------------
(Continue reading)


Gmane