I follow the instructions for compiling TXL on Win32 on pg. 38 of the API manual. I'm using MinGW. All the compiles work fine. The link is the problem. Non of the symbols are being resolved by dxlapi.lib. The error messages are:
Linker error undefined reference to `__getreent'
Linker error undefined reference to `apiPar'
...
Linker error undefined reference to `apiMainProg@28'
When I use nm to view the globals in dxlapi.lib, then begin with an underscore and end with an ampersand followed by an integer. Like the last linker error above, except in dxlapi.lib, the is an underscore, hence the error.
So, apparently, the .lib file has what are called __stdcall decorated names, whereas the .o files are using __cdecl names. I have no idea how to get the linker to resolve these conflicts. I've googled about every term related to this, and cannot seem to get the .lib decorations to link to the .o non-decorations.
Please help.
Bill McCloskey
SystemAdmin - Wed Mar 11 20:41:37 EDT 2009 |
|
Re: Unable to link example application in DOORS API Manual, Pg. 38
Tony_Goodman - Thu Mar 12 05:07:05 EDT 2009
Does anyone actually use this stuff?
|
|
Re: Unable to link example application in DOORS API Manual, Pg. 38
ePiallat - Thu Mar 12 05:35:53 EDT 2009 Tony_Goodman - Thu Mar 12 05:07:05 EDT 2009
Does anyone actually use this stuff?
But I get really frustrated some years ago not being able do.
If you succeed, Bill, I've got a new god ! :worship:
|
|
Re: Unable to link example application in DOORS API Manual, Pg. 38
SystemAdmin - Thu Mar 12 13:58:25 EDT 2009
Well, in terms of who uses this?
This appears to be the ONLY bootstrap "hello world" type application which extends DXL to the realm of linking it with yet another Tool Command Language (aka Tcl), which is awesome in terms of automated testing. The intent: Extend both DXL and Tcl to understand access to the DOORS database AND be able to connect to out target hardware, run an automated test (Tcl seems to sit well with LabView as well,) and then be able to shove the test results back into the DOORS database using the DXL API thus demonstrating requirement satisfaction in a turnkey, pushbutton fashion.
That is one such use. The other use is as a general purpose filter into/out of DOORS to be able to hand object to my favorite tools, filters, script, perl/sed/awk adhoc queries, etc. Oh, my!
And I will resolve the __cdecl/__stdcall calling convention issue. Or DOORS will here about selling us a tool which claims to do certain things, but doesn't deliver. Wonder if this is a Windows/UNIX issue. Like a CR/LF versus LF kind of thing that Telelogic didn't iron out in their port of DOORS from UNIX to broken non-development evironment, yeah, Windows.
Thank you for you current and future input.
Bill
|
|
Re: Unable to link example application in DOORS API Manual, Pg. 38
kbmurphy - Fri Mar 13 15:36:45 EDT 2009 SystemAdmin - Thu Mar 12 13:58:25 EDT 2009
Well, in terms of who uses this?
This appears to be the ONLY bootstrap "hello world" type application which extends DXL to the realm of linking it with yet another Tool Command Language (aka Tcl), which is awesome in terms of automated testing. The intent: Extend both DXL and Tcl to understand access to the DOORS database AND be able to connect to out target hardware, run an automated test (Tcl seems to sit well with LabView as well,) and then be able to shove the test results back into the DOORS database using the DXL API thus demonstrating requirement satisfaction in a turnkey, pushbutton fashion.
That is one such use. The other use is as a general purpose filter into/out of DOORS to be able to hand object to my favorite tools, filters, script, perl/sed/awk adhoc queries, etc. Oh, my!
And I will resolve the __cdecl/__stdcall calling convention issue. Or DOORS will here about selling us a tool which claims to do certain things, but doesn't deliver. Wonder if this is a Windows/UNIX issue. Like a CR/LF versus LF kind of thing that Telelogic didn't iron out in their port of DOORS from UNIX to broken non-development evironment, yeah, Windows.
Thank you for you current and future input.
Bill
Please keep us updated on your journey in getting this to work.
I, for one, wish you the best of luck.
Kevin
|
|