Raúl Huertas | 14 Nov 18:22
Picon

Getting started, compiling errors


Hello. This would be my first time with OpenEXR. I'm writing a little aplication for write a procedural
image(very simple, just for a test) and I have many compilier errors. This is my code:

#include 
#include 
#include 
#include 

const unsigned int TEST_WIDTH = 400;
const unsigned int TEST_HEIGHT = 300;

Rgba misPixeles[TEST_WIDTH*TEST_HEIGHT];

void funnyFillRgbaImage(Rgba* pixeles, int width, int height){
	
	//const int maxIterations = 20.0f;
	const half insideColor[4] = { half(1.0f),half( 0.0f), half(0.0f), half(1.0f)};
	const half outsideColor[4] = { half(0.0f),half( 1.0f), half(0.0f), half(1.0f)};
	
	half color[4] ;
	half radius = 0.0f;
	half x,y;
	for (int i=0; i
_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
Florian Kainz | 14 Nov 19:30

Re: Getting started, compiling errors

Hi Raúl,

I think your code go mangled somewhere on its way
through the email system.  Also, it would help to
know what kind of errors you are getting.

Florian
Raúl Huertas | 14 Nov 19:48
Picon

(no subject)


Sorry, I didn't note how my message was sent. I hope this one works. I hope this time works:

#include OpenEXR/ImfRgba.h //I think hotmail don't accept '<' or '>', but this sysmbols are in my code
#include OpenEXR/ImfRgbaFile.h
#include OpenEXR/ImfIO.h
#include iostream

using namespace Imf;

const unsigned int TEST_WIDTH = 400;
const unsigned int TEST_HEIGHT = 300;

Rgba misPixeles[TEST_WIDTH*TEST_HEIGHT];
	
	

void escribirRgba1(
const char nombreArchivo[],
const Rgba* pixeles,
int width, 
int height
){
	
	RgbaOutputFile file(nombreArchivo, width, height, WRITE_RGBA);
	file.setFrameBuffer( pixeles, 1, width  );
	file.writePixels(height);
	
}//Yes, is the same function of the tutorial

(Continue reading)

Florian Kainz | 14 Nov 20:09

Re: (no subject)

You should not be getting any syntax errors inside the ImfRgbaFile.h
header file.  Either you have a broken header file, or, more likely,
there's a syntax error in your code, before the line where you include
ImfRgbaFile.h.  (I assume that the "#include <OpenEXR/ImfRgba.h>" line
is not the first line in your actual source file.)

Raúl Huertas wrote:
> Sorry, I didn't note how my message was sent. I hope this one works. I hope this time works:
> 
> 
> #include OpenEXR/ImfRgba.h //I think hotmail don't accept '<' or '>', but this sysmbols are in my code
> #include OpenEXR/ImfRgbaFile.h
> #include OpenEXR/ImfIO.h
> #include iostream
> 
> 
> using namespace Imf;
> 
> const unsigned int TEST_WIDTH = 400;
> const unsigned int TEST_HEIGHT = 300;
> 
> Rgba misPixeles[TEST_WIDTH*TEST_HEIGHT];
> 	
> 	
> 
> 
> void escribirRgba1(
> const char nombreArchivo[],
> const Rgba* pixeles,
> int width, 
(Continue reading)

curt stewart | 15 Nov 20:09
Picon
Favicon

.exr codec (?)


Hi, I have a series of noob-ish questions:

I have an HD uncompressed camera rig (www.reel-stream.com) that uses it's own proprietary Mac app to
render out frames. The app will render out (most) any installed Quicktime .mov or image format, I would
like it to render out 16bit frames in .exr. Since I don't have access to the source code for the app I assume
that I would need an .exr codec to output this format.

I've scoured the 'net and have found no such .exr codec for the Mac. So it makes me wonder, does such a thing
even exsist? Or if I want to ouput .exr files, does that require working within the app itself?

If an .exr codec is the way to go, is it difficult to write such a thing under OS X? I searched through the Apple
dev forums and couldn't find any solid examples.

Any tips would be deeply appreciated.

-curt

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
James Vanderhyde | 20 Nov 22:15

Building Visual C++ 2005 for x64 platform

I am trying to build a 64-bit dll of OpenEXR for 64-bit Windows. I’m using Visual Studio 2005 (VC8). I started by downloading the math library (IlmBase) and trying to build the IlmBase solution. I created a configuration for the x64 platform. I had to make a few changes to get the “createDLL” project to compile. I changed the Output Directory and Intermediate Directory to match what the Win32 configuration had. Since the project uses a lot of hard-coded relative paths, these needed to be fixed from Visual Studio’s defaults.

 

This createDLL program runs the linker for the rest of the projects, and it has one line of code that controls the command-line options for the linker. I changed this line to be “X64” instead of “X86.”

 

At this point the “Half” project compiles and links successfully, but when I try to build the “Iex” project I get several linker errors, such as the following:

 

Iex.exp : error LNK2001: unresolved external symbol CTA7?AVErrnoExc <at> Iex <at> <at>

 

All the .lib, .def, and .obj files seem to be OK, so I can’t figure out what the problem is.

 

Does anyone have any tips for me? Thanks.

 

James

 

_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel
Nick Porcino | 21 Nov 03:47

RE: Building Visual C++ 2005 for x64 platform

I haven’t tried this myself, but is it possible that you have a std library mismatch, for example, something set to Multithreaded DLL, and another set to Multithreaded?

 

From: openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org [mailto:openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org] On Behalf Of James Vanderhyde
Sent: Tuesday, November 20, 2007 1:16 PM
To: openexr-devel <at> nongnu.org
Subject: [Openexr-devel] Building Visual C++ 2005 for x64 platform

 

I am trying to build a 64-bit dll of OpenEXR for 64-bit Windows. I’m using Visual Studio 2005 (VC8). I started by downloading the math library (IlmBase) and trying to build the IlmBase solution. I created a configuration for the x64 platform. I had to make a few changes to get the “createDLL” project to compile. I changed the Output Directory and Intermediate Directory to match what the Win32 configuration had. Since the project uses a lot of hard-coded relative paths, these needed to be fixed from Visual Studio’s defaults.

 

This createDLL program runs the linker for the rest of the projects, and it has one line of code that controls the command-line options for the linker. I changed this line to be “X64” instead of “X86.”

 

At this point the “Half” project compiles and links successfully, but when I try to build the “Iex” project I get several linker errors, such as the following:

 

Iex.exp : error LNK2001: unresolved external symbol CTA7?AVErrnoExc <at> Iex <at> <at>

 

All the .lib, .def, and .obj files seem to be OK, so I can’t figure out what the problem is.

 

Does anyone have any tips for me? Thanks.

 

James

 

_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel
James Vanderhyde | 21 Nov 16:22

RE: Building Visual C++ 2005 for x64 platform

All the project settings seem to be in order. Half.dll links fine, but not Iex.dll. It seems like createDLL.cpp is not mangling the symbols in Iex correctly for 64-bit.

 

James

 

From: Nick Porcino [mailto:NPorcino <at> lucasarts.com]
Sent: Tuesday, November 20, 2007 9:48 PM
To: James Vanderhyde; openexr-devel <at> nongnu.org
Subject: RE: [Openexr-devel] Building Visual C++ 2005 for x64 platform

 

I haven’t tried this myself, but is it possible that you have a std library mismatch, for example, something set to Multithreaded DLL, and another set to Multithreaded?

 

From: openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org [mailto:openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org] On Behalf Of James Vanderhyde
Sent: Tuesday, November 20, 2007 1:16 PM
To: openexr-devel <at> nongnu.org
Subject: [Openexr-devel] Building Visual C++ 2005 for x64 platform

 

I am trying to build a 64-bit dll of OpenEXR for 64-bit Windows. I’m using Visual Studio 2005 (VC8). I started by downloading the math library (IlmBase) and trying to build the IlmBase solution. I created a configuration for the x64 platform. I had to make a few changes to get the “createDLL” project to compile. I changed the Output Directory and Intermediate Directory to match what the Win32 configuration had. Since the project uses a lot of hard-coded relative paths, these needed to be fixed from Visual Studio’s defaults.

 

This createDLL program runs the linker for the rest of the projects, and it has one line of code that controls the command-line options for the linker. I changed this line to be “X64” instead of “X86.”

 

At this point the “Half” project compiles and links successfully, but when I try to build the “Iex” project I get several linker errors, such as the following:

 

Iex.exp : error LNK2001: unresolved external symbol CTA7?AVErrnoExc <at> Iex <at> <at>

 

All the .lib, .def, and .obj files seem to be OK, so I can’t figure out what the problem is.

 

Does anyone have any tips for me? Thanks.

 

James

 

_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel
James Vanderhyde | 21 Nov 17:06

RE: Building Visual C++ 2005 for x64 platform

All right, I figured out the problem. The problem is that the format of the .map file changes between linked for 32-bit and linked for 64-bit, and the createDLL.cpp program parses the .map file. The format change is this: every symbol in the .map file that has 1, 2, or 3 initial underscore characters has 0, 1, or 2 underscores (respectively) in the 64-bit .map file. Several places in createDLL.cpp, symbols with two initial underscores are skipped. I changed this to one initial underscore and everything links fine in 64-bit.

 

James

 

 

From: openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org [mailto:openexr-devel-bounces+nporcino=lucasarts.com <at> nongnu.org] On Behalf Of James Vanderhyde
Sent: Tuesday, November 20, 2007 1:16 PM
To: openexr-devel <at> nongnu.org
Subject: [Openexr-devel] Building Visual C++ 2005 for x64 platform

 

I am trying to build a 64-bit dll of OpenEXR for 64-bit Windows. I’m using Visual Studio 2005 (VC8). I started by downloading the math library (IlmBase) and trying to build the IlmBase solution. I created a configuration for the x64 platform. I had to make a few changes to get the “createDLL” project to compile. I changed the Output Directory and Intermediate Directory to match what the Win32 configuration had. Since the project uses a lot of hard-coded relative paths, these needed to be fixed from Visual Studio’s defaults.

 

This createDLL program runs the linker for the rest of the projects, and it has one line of code that controls the command-line options for the linker. I changed this line to be “X64” instead of “X86.”

 

At this point the “Half” project compiles and links successfully, but when I try to build the “Iex” project I get several linker errors, such as the following:

 

Iex.exp : error LNK2001: unresolved external symbol CTA7?AVErrnoExc <at> Iex <at> <at>

 

All the .lib, .def, and .obj files seem to be OK, so I can’t figure out what the problem is.

 

Does anyone have any tips for me? Thanks.

 

James

 

_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel
Hai Nguyen | 26 Nov 19:20
Picon

Static Build Targets

Hi,

I was wondering if there's going to be any static build targets added to 
the Win32 build of OpenEXR.

Thanks

Gmane