quesa-develop — Mailing list for Quesa development

Re: Release 1.7

[James W. W. <os...@jw...>]

On May 4, 2005, at 11:13 AM, Jose' Cruanyes wrote:

> well the error is clear (and that definition indeed solves the  
> problem), so probably is a compiler casting issue.
> I'm away from Tiger now (8:00 PM CET) but can you try C++ casting?
> and going back to gcc 3?

C++ casting does not help (tried both static_cast and  
reinterpret_cast).  Going back to gcc 3 did not help.

>>
>> And why did I only get errors in E3Tesselate.c, not E3GeometryMesh.c?
>>
>
> Strange... a "clean" changes anything?

No.  I did a Clean and rebuilt, and again it showed 12 errors, all in  
E3Tesselate.c.

Re: Release 1.7

[James W. W. <ja...@fr...>]

Jose' Cruanyes <cru...@ce...> wrote:

>I'm away from Tiger now (8:00 PM CET) but can you try C++ casting?
>and going back to gcc 3?
>
>>
>>  And why did I only get errors in E3Tesselate.c, not E3GeometryMesh.c?
>
>Strange... a "clean" changes anything?

I'm away from Tiger too now.  Back in 6 or 7 hours.
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>

Re: Release 1.7

[Jose' C. <cru...@ce...>]

Il giorno 04/mag/05, alle 20:00, James W. Walker ha scritto:

>> it should be for tiger
>> typedef GLvoid (CALLBACK * GLcallback)(...);
>>
>> instead of
>> typedef void (CALLBACK * GLcallback)();
>
> How do you know that?  In the Tiger framework headers, gluTessCallback 
> is declared as
>
> extern void gluTessCallback (GLUtesselator* tess, GLenum which, GLvoid 
> (*CallBackFunc)());
>
> no ellipsis.

well the error is clear (and that definition indeed solves the 
problem), so probably is a compiler casting issue.
I'm away from Tiger now (8:00 PM CET) but can you try C++ casting?
and going back to gcc 3?

>
> And why did I only get errors in E3Tesselate.c, not E3GeometryMesh.c?

Strange... a "clean" changes anything?

>
Pax et Bonum

# dott. Jose' Cruanyes Aguilar  -  C.E. Soft srl
#  Pzza. Firenze,4 MILANO  -  XX Settembre 10, CREMONA
#   02,33603122                0372,460602

Re: Release 1.7

[James W. W. <ja...@fr...>]

Jose' Cruanyes <cru...@ce...> wrote:

>the problem is the definition of GLcallback in E3GeometryMesh.c and 
>E3Tesselate.c
>
>it should be for tiger
>typedef GLvoid (CALLBACK * GLcallback)(...);
>
>instead of
>typedef void (CALLBACK * GLcallback)();

How do you know that?  In the Tiger framework headers, 
gluTessCallback is declared as

extern void gluTessCallback (GLUtesselator* tess, GLenum which, 
GLvoid (*CallBackFunc)());

no ellipsis.

And why did I only get errors in E3Tesselate.c, not E3GeometryMesh.c?

>
>the problem is the latter doesn't compile in Tiger and the first 
>doesn't compile in other cases
>
>probably we should move the definition to GLPrefix.h, the problem 
>remains (how detect we're compiling with tiger?
>
>is a gcc4 problem or a headers one?
>what if compiling with CW using the 10.4 SDK?

The problem does not occur in CodeWarrior under Tiger.
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>

Re: Release 1.7

[Jose' C. <cru...@ce...>]

Il giorno 04/mag/05, alle 19:16, James W. Walker ha scritto:

> Yes, I got those errors in E3Tessellate.c in XCode under Tiger. 
> CodeWarrior does not given any error messages.  I don't understand the 
> error messages.  I posted some questions about this on the XCode-users 
> mailing list, but got no replies.
>

the problem is the definition of GLcallback in E3GeometryMesh.c and 
E3Tesselate.c

it should be for tiger
typedef GLvoid (CALLBACK * GLcallback)(...);

instead of
typedef void (CALLBACK * GLcallback)();

the problem is the latter doesn't compile in Tiger and the first 
doesn't compile in other cases

probably we should move the definition to GLPrefix.h, the problem 
remains (how detect we're compiling with tiger?

is a gcc4 problem or a headers one?
what if compiling with CW using the 10.4 SDK?

Pax et Bonum

# dott. Jose' Cruanyes Aguilar  -  C.E. Soft srl
#  Pzza. Firenze,4 MILANO  -  XX Settembre 10, CREMONA
#   02,33603122                0372,460602

Re: Release 1.7

[James W. W. <ja...@fr...>]

Peter Michelsen <Pet...@mi...> wrote:

>I have just been having a play with Quesa Release 1.7 on Tiger and 
>found some errors. I had this in the pre-release version of Tiger as 
>well but I just commented then out.
>I could fix them but I am not to sure on the code....
>
>The fix was to change the void* into GLvoid* and then add some dots?
>
>Has anyone else had these errors.

Yes, I got those errors in E3Tessellate.c in XCode under Tiger. 
CodeWarrior does not given any error messages.  I don't understand 
the error messages.  I posted some questions about this on the 
XCode-users mailing list, but got no replies.
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>

Re: Release 1.7

[Peter M. <Pet...@mi...>]

Hi All,

I have just been having a play with Quesa Release 1.7 on Tiger and 
found some errors. I had this in the pre-release version of Tiger as 
well but I just commented then out.
I could fix them but I am not to sure on the code....

The fix was to change the void* into GLvoid* and then add some dots?

Has anyone else had these errors.

The fix can wait until the next release, as I am just about to start on 
view hints export.

Beyond that the release looks good.

Cheers Peter.


On 2 May 2005, at 20:07, James W. Walker wrote:

> "Sean McBride" <se...@ro...> wrote:
>
>> But I'd suggest renaming:
>>
>> /Developers/Stub Libraries/
>> to
>> /Developers/Stub Libraries (CFM)/
>>
>> to be consistent.
>
> OK.
>
>>  Also adding a
>>
>> /Developers/Static Libraries (Mach-O)/
>>
>> would be nice.  And Jose's static lib addition to the xcode projects
>> builds nicely.
>
> Actually, I got some errors when I tried to build that under Tiger.
>
>> However, I get the following link errors using the xcode-built static 
>> lib
>> with a CW project.  Quesa uses C++ now, right?  Am I doomed by
>> differences in C++ ABI between compilers?
>
> Yes, I think you're doomed. It's probably not only the ABI, but the 
> fact that they are using different STL implementations.  Why do you 
> prefer using a static lib rather than a framework?
> -- 
>   James W. Walker, ScriptPerfection Enterprises, Inc.
>   <http://www.write-brain.com/>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great 
> events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Quesa-develop mailing list
> Que...@li...
> https://lists.sourceforge.net/lists/listinfo/quesa-develop
>
> -- 
> This message has been scanned for viruses and
> dangerous content by Swift Internet, and is
> believed to be clean.
>

Re: Release 1.7

[Jose' C. <cru...@ce...>]

Il giorno 02/mag/05, alle 00:32, James W. Walker ha scritto:

> I've prepared packages for a 1.7 release.  They are posted for your 
> examination at:
>
> <ftp://ftp.jwwalker.com/misc/quesa_1.7_sdk_mac.dmg>
> <ftp://ftp.jwwalker.com/misc/quesa_1.7_sdk_win32.zip>
> <ftp://ftp.jwwalker.com/misc/quesa_1.7_source_mac.dmg>
> <ftp://ftp.jwwalker.com/misc/quesa_1.7_source_win32.zip>

done also for unix

<http://cremona.cegroup.it/quesa-1.7.tar.gz>
<http://cremona.cegroup.it/quesaexamples-1.7.tar.gz>


Pax et Bonum

# dott. Jose' Cruanyes Aguilar  -  C.E. Soft srl
#  Pzza. Firenze,4 MILANO  -  XX Settembre 10, CREMONA
#   02,33603122                0372,460602

Re: Release 1.7

[Sean M. <se...@ro...>]

On 2005-05-02 14:30, James W. Walker said:

>And this is not a case where you could use =
Q3Point3D=5FTo3DTransformArray=3F

Didn't know about it. :)  I'll check it out, thanks!

>>2) because I figured it'd get rid of these link warnings when I use the
>>framework:
>
>Hmm.  This is new to me, but I haven't tried using the Quesa 
>framework in an app built with XCode.

I build my app with both cw and xcode, and get the warnings with either one.

>Does your app use prebinding=3F 
>Can you turn that off=3F  I hear that Apple no longer recommends that 
>apps use prebinding.  Alternatively, I wonder if I should check the 
>"disable prebinding" options in the CodeWarrior project for the 
>framework=3F

Well, I ditched the static lib and now am using the 1.7 framework, and
the link warnings are gone! Dunno why, but I'm happy. :)

Thanks!

-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

[ quesa-Bugs-1194603 ] Transparency problem with rasterize camera transforms

[SourceForge.net <no...@so...>]

Bugs item #1194603, was opened at 2005-05-03 13:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442052&aid=1194603&group_id=45158

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Frank Condello (pox)
Assigned to: Nobody/Anonymous (nobody)
Summary: Transparency problem with rasterize camera transforms

Initial Comment:
Transparent triangles with Z coordinates other than zero aren't drawn 
when using rasterize camera transforms. The problem lies in 
ir_geom_transparent_add, where triangles "behind" the camera are 
culled. Rasterize transforms invert Z, which is likely confusing the 
culling check.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442052&aid=1194603&group_id=45158

Re: Release 1.7

[James W. W. <ja...@fr...>]

"Sean McBride" <se...@ro...> wrote:

>>Why do you
>>prefer using a static lib rather than a framework?
>
>1) because I call Q3Point3D_Transform() in a tight loop and Shark was
>saying something about dynamic PIC stuff (forget exactly) so I thought I
>might get a little performance boost.

And this is not a case where you could use Q3Point3D_To3DTransformArray?

>
>2) because I figured it'd get rid of these link warnings when I use the
>framework:

Hmm.  This is new to me, but I haven't tried using the Quesa 
framework in an app built with XCode.  Does your app use prebinding? 
Can you turn that off?  I hear that Apple no longer recommends that 
apps use prebinding.  Alternatively, I wonder if I should check the 
"disable prebinding" options in the CodeWarrior project for the 
framework?
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>

Bug with rasterize camera transforms and transparent objects

[Frank C. <dev...@ch...>]

When using a rasterize camera transform, any transparent triangles with 
Z coordinates other than 0 aren't drawn. The problem lies in 
ir_geom_transparent_add, where triangles "behind" the camera are culled 
- this doesn't seem to work with rasterize transforms, probably because 
Z is inverted.

I haven't looked into the problem further, but disabling the culling 
altogether restores the expected behaviour (at the cost over possible 
overdraw).

Frank.

Re: Release 1.7

[Sean M. <se...@ro...>]

On 2005-05-02 12:07, James W. Walker said:

>>  Also adding a
>>
>>/Developers/Static Libraries (Mach-O)/
>>
>>would be nice.  And Jose's static lib addition to the xcode projects
>>builds nicely.
>
>Actually, I got some errors when I tried to build that under Tiger.

I built in under 10.3.9, there were hundreds of warnings but no errors.

>>However, I get the following link errors using the xcode-built static lib
>>with a CW project.  Quesa uses C++ now, right=3F  Am I doomed by
>>differences in C++ ABI between compilers=3F
>
>Yes, I think you're doomed. It's probably not only the ABI, but the 
>fact that they are using different STL implementations.

Yeah, damn. :(

>Why do you 
>prefer using a static lib rather than a framework=3F

1) because I call Q3Point3D=5FTransform() in a tight loop and Shark was
saying something about dynamic PIC stuff (forget exactly) so I thought I
might get a little performance boost.

2) because I figured it'd get rid of these link warnings when I use the
framework:

dynamic library '@executable=5Fpath/../Frameworks/Quesa.framework/Versions/
A/Quesa' section '=5F=5FTEXT' ($00000000-$0010F000)
overlaps with output file section '=5F=5FPAGEZERO' ($00000000-$00001000)
(need to run redo=5Fprebinding)

dynamic library '@executable=5Fpath/../Frameworks/Quesa.framework/Versions/
A/Quesa' section '=5F=5FTEXT' ($00000000-$0010F000)
overlaps with output file section '=5F=5FTEXT' ($00001000-$000A8000)
(need to run redo=5Fprebinding)

dynamic library '@executable=5Fpath/../Frameworks/Quesa.framework/Versions/
A/Quesa' section '=5F=5FTEXT' ($00000000-$0010F000)
overlaps with output file section '=5F=5FDATA' ($000A8000-$000AF000)
(need to run redo=5Fprebinding)

dynamic library '@executable=5Fpath/../Frameworks/Quesa.framework/Versions/
A/Quesa' section '=5F=5FTEXT' ($00000000-$0010F000)
overlaps with output file section '=5F=5FOBJC' ($000AF000-$000B3000)
(need to run redo=5Fprebinding)

dynamic library '@executable=5Fpath/../Frameworks/Quesa.framework/Versions/
A/Quesa' section '=5F=5FTEXT' ($00000000-$0010F000)
overlaps with output file section '=5F=5FLINKEDIT' ($000B3000-$00166000)
(need to run redo=5Fprebinding)


-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

Re: Release 1.7

[James W. W. <ja...@fr...>]

"Sean McBride" <se...@ro...> wrote:

>But I'd suggest renaming:
>
>/Developers/Stub Libraries/
>to
>/Developers/Stub Libraries (CFM)/
>
>to be consistent.

OK.

>  Also adding a
>
>/Developers/Static Libraries (Mach-O)/
>
>would be nice.  And Jose's static lib addition to the xcode projects
>builds nicely.

Actually, I got some errors when I tried to build that under Tiger.

>However, I get the following link errors using the xcode-built static lib
>with a CW project.  Quesa uses C++ now, right?  Am I doomed by
>differences in C++ ABI between compilers?

Yes, I think you're doomed. It's probably not only the ABI, but the 
fact that they are using different STL implementations.  Why do you 
prefer using a static lib rather than a framework?
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>

Re: Release 1.7

[Sean M. <se...@ro...>]

On 2005-05-01 15:32, James W. Walker said:

>I've prepared packages for a 1.7 release.  They are posted for your  
>examination at:

I like the file layout!

But I'd suggest renaming:

/Developers/Stub Libraries/
to
/Developers/Stub Libraries (CFM)/

to be consistent. Also adding a

/Developers/Static Libraries (Mach-O)/

would be nice.  And Jose's static lib addition to the xcode projects
builds nicely.

However, I get the following link errors using the xcode-built static lib
with a CW project.  Quesa uses C++ now, right=3F  Am I doomed by
differences in C++ ABI between compilers=3F



Link Error   : undefined: 'std::string::c=5Fstr()const ' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: 'std::string::resize(unsigned long)' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: 'std::string::operator[](unsigned long)' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: 'std::string::size()const ' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: 'std::string::empty()const ' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: 'std::allocator<char>::~allocator()' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: '=5F=5Fcxa=5Fend=5Fcatch' (code)
Referenced from 'std::vector<void*, std::allocator<void*> >:
:=5FM=5Finsert=5Faux(=5F=5Fgnu=5Fcxx::=5F=5Fnormal=5Fiterator<void**, =
=5F=5Fgnu=5Fcxx:
:=5F=5Fnormal=5Fiterator>, const void*&)' in libQuesa.a
Referenced from 'std::list<TQ3TextureCache, std:
:allocator<TQ3TextureCache> >::=5FM=5Fcreate=5Fnode(const =
TQ3TextureCache&)' in
libQuesa.a
Referenced from 'std::list<TQ3CachedTexture, std:
:allocator<TQ3CachedTexture> >::=5FM=5Fcreate=5Fnode(const =
TQ3CachedTexture&)'
in libQuesa.a
Referenced from 'gltexturemgr=5FInitList()' in libQuesa.a
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a
Referenced from 'std::vector<=5FGLOBAL=5F
=5FN=5F=5FUsers=5Fsean=5FDesktop=5Fquesa=5F1.7=5Fsour
ce=5FDevelopment=5FSource=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DMF=5FT=
ext.cWG5Zyb:
:TOCEntry, std::allocator<=5FGLOBAL=5F=5FN=5F
=5FUsers=5Fsean=5FDesktop=5Fquesa=5F1.7=5Fsource=5F
Development=5FSource=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DM' in =
libQuesa.a
Referenced from '=5FZSt24=5F=5Funinitialize
d=5Fcopy=5FauxIN9=5F=5Fgnu=5Fcxx17=5F=5Fnormal=5Fiter
atorIPN115=5FGLOBAL=5F=5FN=5F=5FUsers=5Fsean=5FDesk
top=5Fquesa=5F1.7=5Fsource=5FDevelopment=5FSour
ce=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DM
=46=5FText.cWG5Zyb8TOCEntryESt6vectorIS3=5F
SaIS3=5FEEEES8=5FET0=5FT=5FSA=5FS9=5F12=5F=5Ffalse=5Ftype' in libQuesa.a
Referenced from 'std::=5FRb=5Ftree<std::string, std::pair<const std::string,
unsigned long>, std::=5FSelect1st<pair<const std::string, unsigned long> >,
std::less<std::string>, std::allocator<pair<const std::string, unsigned
long> > >::=5FM=5Fcreate=5Fnode(const pair<const std::strin' in libQuesa.a

Link Error   : undefined: '=5F=5Fcxa=5Frethrow' (code)
Referenced from 'std::vector<void*, std::allocator<void*> >:
:=5FM=5Finsert=5Faux(=5F=5Fgnu=5Fcxx::=5F=5Fnormal=5Fiterator<void**, =
=5F=5Fgnu=5Fcxx:
:=5F=5Fnormal=5Fiterator>, const void*&)' in libQuesa.a
Referenced from 'std::list<TQ3TextureCache, std:
:allocator<TQ3TextureCache> >::=5FM=5Fcreate=5Fnode(const =
TQ3TextureCache&)' in
libQuesa.a
Referenced from 'std::list<TQ3CachedTexture, std:
:allocator<TQ3CachedTexture> >::=5FM=5Fcreate=5Fnode(const =
TQ3CachedTexture&)'
in libQuesa.a
Referenced from 'std::vector<=5FGLOBAL=5F
=5FN=5F=5FUsers=5Fsean=5FDesktop=5Fquesa=5F1.7=5Fsour
ce=5FDevelopment=5FSource=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DMF=5FT=
ext.cWG5Zyb:
:TOCEntry, std::allocator<=5FGLOBAL=5F=5FN=5F
=5FUsers=5Fsean=5FDesktop=5Fquesa=5F1.7=5Fsource=5F
Development=5FSource=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DM' in =
libQuesa.a
Referenced from '=5FZSt24=5F=5Funinitialize
d=5Fcopy=5FauxIN9=5F=5Fgnu=5Fcxx17=5F=5Fnormal=5Fiter
atorIPN115=5FGLOBAL=5F=5FN=5F=5FUsers=5Fsean=5FDesk
top=5Fquesa=5F1.7=5Fsource=5FDevelopment=5FSour
ce=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DM
=46=5FText.cWG5Zyb8TOCEntryESt6vectorIS3=5F
SaIS3=5FEEEES8=5FET0=5FT=5FSA=5FS9=5F12=5F=5Ffalse=5Ftype' in libQuesa.a
Referenced from 'std::=5FRb=5Ftree<std::string, std::pair<const std::string,
unsigned long>, std::=5FSelect1st<pair<const std::string, unsigned long> >,
std::less<std::string>, std::allocator<pair<const std::string, unsigned
long> > >::=5FM=5Fcreate=5Fnode(const pair<const std::strin' in libQuesa.a

Link Error   : undefined: '=5F=5Fcxa=5Fbegin=5Fcatch' (code)
Referenced from 'std::vector<void*, std::allocator<void*> >:
:=5FM=5Finsert=5Faux(=5F=5Fgnu=5Fcxx::=5F=5Fnormal=5Fiterator<void**, =
=5F=5Fgnu=5Fcxx:
:=5F=5Fnormal=5Fiterator>, const void*&)' in libQuesa.a
Referenced from 'std::list<TQ3TextureCache, std:
:allocator<TQ3TextureCache> >::=5FM=5Fcreate=5Fnode(const =
TQ3TextureCache&)' in
libQuesa.a
Referenced from 'std::list<TQ3CachedTexture, std:
:allocator<TQ3CachedTexture> >::=5FM=5Fcreate=5Fnode(const =
TQ3CachedTexture&)'
in libQuesa.a
Referenced from 'gltexturemgr=5FInitList()' in libQuesa.a
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a
Referenced from 'std::vector<=5FGLOBAL=5F
=5FN=5F=5FUsers=5Fsean=5FDesktop=5Fquesa=5F1.7=5Fsour
ce=5FDevelopment=5FSource=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DMF=5FT=
ext.cWG5Zyb:
:TOCEntry, std::allocator<=5FGLOBAL=5F=5FN=5F
=5FUsers=5Fsean=5FDesktop=5Fquesa=5F1.7=5Fsource=5F
Development=5FSource=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DM' in =
libQuesa.a
Referenced from '=5FZSt24=5F=5Funinitialize
d=5Fcopy=5FauxIN9=5F=5Fgnu=5Fcxx17=5F=5Fnormal=5Fiter
atorIPN115=5FGLOBAL=5F=5FN=5F=5FUsers=5Fsean=5FDesk
top=5Fquesa=5F1.7=5Fsource=5FDevelopment=5FSour
ce=5FFileFormats=5FReaders=5F3DMF=5FE3FFR=5F3DM
=46=5FText.cWG5Zyb8TOCEntryESt6vectorIS3=5F
SaIS3=5FEEEES8=5FET0=5FT=5FSA=5FS9=5F12=5F=5Ffalse=5Ftype' in libQuesa.a
Referenced from 'std::=5FRb=5Ftree<std::string, std::pair<const std::string,
unsigned long>, std::=5FSelect1st<pair<const std::string, unsigned long> >,
std::less<std::string>, std::allocator<pair<const std::string, unsigned
long> > >::=5FM=5Fcreate=5Fnode(const pair<const std::strin' in libQuesa.a

Link Error   : undefined: 'std::string::string(const char*, const std:
:allocator<char>&)' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: 'std::allocator<char>::allocator()' (code)
Referenced from =
'e3fformat=5F3dmf=5Ftext=5Fskipcomments(E3Text3DMFReader*)' in
libQuesa.a

Link Error   : undefined: 'std::=5F=5Fdefault=5Falloc=5Ftemplate<true, 0>:
:deallocate(void*, unsigned long)' (code)
Referenced from =
'std::=5F=5Fsimple=5Falloc<std::=5FList=5Fnode<TQ3TextureCache>,
std::=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >:
:deallocate(=5FList=5Fnode<TQ3TextureCache>*, unsigned long)' in libQuesa.a
Referenced from 'std::=5F=5Fsimple=5Falloc<void*, std:
:=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >::deallocate(void**, unsigned =
long)'
in libQuesa.a
Referenced from =
'std::=5F=5Fsimple=5Falloc<std::=5FList=5Fnode<TQ3CachedTexture>,
std::=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >:
:deallocate(=5FList=5Fnode<TQ3CachedTexture>*, unsigned long)' in libQuesa.a
Referenced from 'std::=5F=5Fsimple=5Falloc<
=5FGLOBAL=5F=5FN=5F=5FUsers=5Fsean=5FDesktop=5Fquesa=5F
1.7=5Fsource=5FDevelopment=5FSource=5FFileFor
mats=5FReaders=5F3DMF=5FE3FFR=5F3DMF=5FText.cWG5Zyb::TOCEntry, std:
:=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >:
:deallocate(=5FGLOBAL=5F=5FN=5F=5FUsers=5Fsean=5FDesktop=5Fquesa=5F1.7=5Fso=
urce=5FDevelop' in
libQuesa.a
Referenced from =
'std::=5F=5Fsimple=5Falloc<std::=5FRb=5Ftree=5Fnode<std::pair<const
std::string, unsigned long> >, std::=5F=5Fdefault=5Falloc=5Ftemplate<true, =
0> >:
:deallocate(=5FRb=5Ftree=5Fnode<std::pair<const std::string, unsigned =
long> >*,
unsigned long)' in libQuesa.a

Link Error   : undefined: 'std::=5F=5Fdefault=5Falloc=5Ftemplate<true, 0>:
:allocate(unsigned long)' (code)
Referenced from 'std::=5F=5Fsimple=5Falloc<void*, std:
:=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >::allocate(unsigned long)' in =
libQuesa.a
Referenced from =
'std::=5F=5Fsimple=5Falloc<std::=5FList=5Fnode<TQ3CachedTexture>,
std::=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >::allocate(unsigned long)' =
in
libQuesa.a
Referenced from =
'std::=5F=5Fsimple=5Falloc<std::=5FList=5Fnode<TQ3TextureCache>,
std::=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >::allocate(unsigned long)' =
in
libQuesa.a
Referenced from 'std::=5F=5Fsimple=5Falloc<
=5FGLOBAL=5F=5FN=5F=5FUsers=5Fsean=5FDesktop=5Fquesa=5F
1.7=5Fsource=5FDevelopment=5FSource=5FFileFor
mats=5FReaders=5F3DMF=5FE3FFR=5F3DMF=5FText.cWG5Zyb::TOCEntry, std:
:=5F=5Fdefault=5Falloc=5Ftemplate<true, 0> >::allocate(unsigned long)' in =
libQuesa.a
Referenced from =
'std::=5F=5Fsimple=5Falloc<std::=5FRb=5Ftree=5Fnode<std::pair<const
std::string, unsigned long> >, std::=5F=5Fdefault=5Falloc=5Ftemplate<true, =
0> >:
:allocate(unsigned long)' in libQuesa.a



-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

Re: Release 1.7

[Sean M. <se...@ro...>]

On 2005-05-02 10:39, James W. Walker said:

>It's working for me now

Me too... weird... nothing to see here... move along :)

-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

Re: Release 1.7

[James W. W. <ja...@fr...>]

"Sean McBride" <se...@ro...> wrote:

>On 2005-05-01 15:32, James W. Walker said:
>
>>I've prepared packages for a 1.7 release.  They are posted for your
>>examination at:
>>
>><ftp://ftp.jwwalker.com/misc/quesa_1.7_sdk_mac.dmg>
>><ftp://ftp.jwwalker.com/misc/quesa_1.7_sdk_win32.zip>
>><ftp://ftp.jwwalker.com/misc/quesa_1.7_source_mac.dmg>
>><ftp://ftp.jwwalker.com/misc/quesa_1.7_source_win32.zip>
>
>Is it just me or is that server down?

It's working for me now, and the ISP's system notices page is not 
showing any down-time for that server since I posted the files.
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>

Re: Release 1.7

[Sean M. <se...@ro...>]

On 2005-05-01 15:32, James W. Walker said:

>I've prepared packages for a 1.7 release.  They are posted for your  
>examination at:
>
><ftp://ftp.jwwalker.com/misc/quesa=5F1.7=5Fsdk=5Fmac.dmg>
><ftp://ftp.jwwalker.com/misc/quesa=5F1.7=5Fsdk=5Fwin32.zip>
><ftp://ftp.jwwalker.com/misc/quesa=5F1.7=5Fsource=5Fmac.dmg>
><ftp://ftp.jwwalker.com/misc/quesa=5F1.7=5Fsource=5Fwin32.zip>

Is it just me or is that server down=3F

-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

Release 1.7

[James W. W. <os...@jw...>]

I've prepared packages for a 1.7 release.  They are posted for your =20
examination at:

<ftp://ftp.jwwalker.com/misc/quesa_1.7_sdk_mac.dmg>
<ftp://ftp.jwwalker.com/misc/quesa_1.7_sdk_win32.zip>
<ftp://ftp.jwwalker.com/misc/quesa_1.7_source_mac.dmg>
<ftp://ftp.jwwalker.com/misc/quesa_1.7_source_win32.zip>

If I recall correctly, we hadn't  really come to a consensus about a =20
version number, but Jos=E9 agreed with me that it should be 1.7.  =20
Others might prefer 1.7b1 or 1.7d1.  My argument is that since we =20
make releases rather infrequently, it is not practical to try to =20
stick to a traditional development/alpha/beta/release pattern or to =20
have separate development/stable tracks.  The fact that it's been two =20=

and a half months since we started discussing a release tends to =20
support my position, IMHO.

Another possibly-controversial matter is the file format.  Apple is =20
no longer bundling StuffIt Expander with the OS, so I think we should =20=

consider switching to .dmg or .zip for Mac archives.  It is tempting =20
to use .zip for all platforms, but non-Mac users may be puzzled or =20
annoyed by the __MACOSX folder produced by unzipping an archive with =20
Mac information.  I have provisionally used .dmg format, but let me =20
know what you think.

I've made a few change in the content of the SDKs:

* I included the API reference.  It just seems like something that =20
would be expected in an SDK.

* In the Mac SDK, I added Mach-O frameworks.

* In the Mac SDK, I did not include the classic libraries.  Note that =20=

this does not mean that I have dropped all support for OS 9, since =20
Carbon libraries can be used in OS 9.

* In the Mac SDK, I included the Quesa Model Viewer.  (As far as I =20
know, this has not been implemented for Windows.)

Re: Looking for Quesa mach-O static lib (for Mac OS X)

[Sean M. <se...@ro...>]

On 2005-04-11 11:40, Jose' Cruanyes said:

>I've uploaded on CVS a patch that adds a target in the xCode project to 
>build a libQuesa.a

Cool, thanks.  I guess I'll grab it from CVS, or maybe wait for the next
release.

-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

Re: Looking for Quesa mach-O static lib (for Mac OS X)

[Jose' C. <cru...@ce...>]

Il giorno 08/apr/05, alle 19:11, Sean McBride ha scritto:

> Hi again!
>
> Well, after getting Quesa to build as a framework, I've decided, in the
> end, that I would prefer having Quesa as a static lib. ie a 
> "libQuesa.a".
>
> Is there an existing project that builds a libQuesa.a?
>
> Thanks!
>

I've uploaded on CVS a patch that adds a target in the xCode project to 
build a libQuesa.a

alternatively you can compile using the unix chaintool (see 
Development/Projects/Unix/INSTALL.fullDist)

Note that it's not the same thing, since the unix build depends on GTK 
and the xcode build uses Cocoa


Pax et Bonum

# dott. Jose' Cruanyes Aguilar  -  C.E. Soft srl
#  Pzza. Firenze,4 MILANO  -  XX Settembre 10, CREMONA
#   02,33603122                0372,460602

Looking for Quesa mach-O static lib (for Mac OS X)

[Sean M. <se...@ro...>]

Hi again!

Well, after getting Quesa to build as a framework, I've decided, in the
end, that I would prefer having Quesa as a static lib. ie a "libQuesa.a".

Is there an existing project that builds a libQuesa.a=3F

Thanks!

-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

Re: Looking for pre-built Mach-O Quesa framework

[Sean M. <se...@ro...>]

On 2005-03-31 09:01, James W. Walker said:

>In theory the Xcode project should have worked, but I guess we messed 

It seems only GLTextureManager.c needed to be added.  Now it builds.  I
also had to change the headers' "role" to "public" to get them into the
framework.

>up.  Look for "Quesa Framework.mcp.xml".  Choose that with "Import 
>Project" in CodeWarrior 9.

Damn, I dunno how I missed it!  I guess since it has a generic icon.  It
compiles, but doesn't build either:

"Will not record build dependency for source file "Quesa.plc" generating
file "Info.plist" as the IDE could not locate the generated file along an
access path.

Package: Headers: Could not find item "Headers" to symlink."


Anyway, now that it's built, my project is now able to include Quesa.h
and link to the framework

Happily Quesa.h gives only 3 warnings with CW 9.4:

Warning : undefined macro '=5F=5Fdest=5Fos' used in #if or #elif conditional
Quesa.h line 60    #if ((defined(=5F=5FMWERKS=5F=5F) && =5F=5Fdest=5Fos =
=3D=3D =5F=5Fmac=5Fos) ||
defined(MPW=5FCPLUS) || defined(MPW=5FC)) 
Project: RRCropViewTest.mcp, Target: Cocoa Debug, Source File:
RRMainWindowController.m

Warning : undefined macro '=5F=5Fmac=5Fos' used in #if or #elif conditional
Quesa.h line 60    #if ((defined(=5F=5FMWERKS=5F=5F) && =5F=5Fdest=5Fos =
=3D=3D =5F=5Fmac=5Fos) ||
defined(MPW=5FCPLUS) || defined(MPW=5FC)) 
Project: RRCropViewTest.mcp, Target: Cocoa Debug, Source File:
RRMainWindowController.m

Warning : undefined macro '=5F=5FINTEL=5F=5F' used in #if or #elif =
conditional
Quesa.h line 68    #if (defined(=5FMSC=5FVER) || =
(defined(=5F=5FMWERKS=5F=5F) &&
=5F=5FINTEL=5F=5F)) 
Project: RRCropViewTest.mcp, Target: Cocoa Debug, Source File:
RRMainWindowController.m

but with XCode 1.5 I get an #error:

    #error Target OS not selected!

It was easy enough to work around.

Thanks!

-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada

Re: Looking for pre-built Mach-O Quesa framework

[James W. W. <os...@jw...>]

On Mar 31, 2005, at 7:46 AM, Sean McBride wrote:

> So next I downloaded "quesa_1.6d20_source" and poked around. /
> quesa_1.6d20_source/Development/Projects/Mac/Quesa.mcp seems to be CFM
> only.  I next tried Quesa.xcode but it fails to build, with 362 
> warnings
> and 1 error:

In theory the Xcode project should have worked, but I guess we messed 
up.  Look for "Quesa Framework.mcp.xml".  Choose that with "Import 
Project" in CodeWarrior 9.  However, I'd suggest that you get the 
sources from CVS, as we are overdue for a release.
--
<http://www.jwwalker.com/>

Looking for pre-built Mach-O Quesa framework

[Sean M. <se...@ro...>]

Hello!

I am a Quesa newbie and am considering using it for it's 4x4 Matrix math
functions (and nothing more).  I am hoping to be able to add a Quesa
framework to my project and #include "Quesa/Quesa.h" and presto! :)

My project is a Mach-O Cocoa application; I have CW 9.4 and XCode 1.5
projects, I am using OS 10.3.8.  I downloaded "quesa=5F1.6d20=5Fsdk=5Fmac" =
but
all I see are CFM libraries.  I read in "Release Notes.txt" a reference
to a Mach-O framework, but it seems to be missing.

So next I downloaded "quesa=5F1.6d20=5Fsource" and poked around. /
quesa=5F1.6d20=5Fsource/Development/Projects/Mac/Quesa.mcp seems to be CFM
only.  I next tried Quesa.xcode but it fails to build, with 362 warnings
and 1 error:

ld: Undefined symbols:
=5FGLTextureMgr=5FAddContext
=5FGLTextureMgr=5FGetNextSharingBase
=5FGLTextureMgr=5FGetTextureCache
=5FGLTextureMgr=5FRemoveContext

Is there a pre-built Mach-O framework out there=3F  If not, which project
should I be building=3F

Thanks!

-- 
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montr=E9al, Qu=E9bec, Canada