Compile XSLSample.c or XSLSample.cpp error

Hi,
I got tons of error messages when I compiled XSLSample.c or cpp file under the Microsoft VC++6.0. I set the additional include directory to e:\cpporaclexslt\include (where contains the header files) and also set the additional modules to e:\cpporaclexslt\lib. the following shows the errors:
Compiling...
XSLSample.c
e:\coraclexslt\include\oraxml.h(54) : error C2143: syntax error : missing ')' before '*'
e:\coraclexslt\include\oraxml.h(54) : error C2143: syntax error : missing ';' before '*'
e:\coraclexslt\include\oraxml.h(54) : error C2059: syntax error : '*'
e:\coraclexslt\include\oraxml.h(55) : error C2059: syntax error : ')'
e:\coraclexslt\include\oraxml.h(56) : error C2143: syntax error : missing ')' before '*'
e:\coraclexslt\include\oraxml.h(56) : error C2143: syntax error : missing '{' before '*'
e:\coraclexslt\include\oraxml.h(56) : error C2059: syntax error : ')'
e:\coraclexslt\include\oraxml.h(57) : error C2143: syntax error : missing ')' before '*'
e:\coraclexslt\include\oraxml.h(57) : error C2143: syntax error : missing '{' before '*'
e:\coraclexslt\include\oraxml.h(57) : warning C4142: benign redefinition of type
I'll appreciate it if you help me out.
Jingkun

Bug logged andy.
B

Similar Messages

Windows LV6.0 running on Linux Wine: config.cpp error (line 404)

Have anyone tried to run LabView (Windows version) under Linux using the Wine "emulator"?
Trying this on Debian Woody, with a Win98 install of LabView 6.0 returns:
config.cpp error (line 404)
I tried to search for such a file on both Win/Linux partitions: there's none.
So how am i gonna check this line 404?
Any clue would be strongly welcome!

I agree with Labviewguru about getting Labview for Linux. The only
problem is that you have to dish out $2000 or $3500. They don't have a
Base package.
I'm not sure if NI recomends a particular window manager but I do know it
will run on any of them. In an extreme case I used it on a PII 233MHz,
64MB ram, and a 300 MB disk. It was a Slackware distro using the fvwm2
window manager. Ran great. Presently I run it with Gnome.
My point is that if you have to buy a LV for Linux license, at least you
can save money buy putting it on a machine that's been used as a paper
weight for several years.
-kevin
In article <[email protected]>,
"Labviewguru" wrote:
> I don't believe you can run LabVIEW in an e
mulation environment. There
> is too much system control that LabVIEW needs a handle on to be able to
> run on an emulator.
>
> The reason you are not able to find and troubleshoot that file is
> because it is part of the source code for LabVIEW, and doesn't exist
> except in a super secret vault which may or may not be located in Austin
> Texas...
>
> Are you aware that there is a version of LabVIEW for Linux? I believe
> that they recommend running KDE or similar GUI, but check on the support
> website for that at ni.com/linux.
>
> I hope that was enough of a clue...

Labview 6.0.2 patch does not remove my "image.cpp" error

I have an industrial PC with the following characteristics:
* Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours only option)
* ROBO 608, Industrial SBC motherboard with onboard video driver, from Chips and Technologies, 69000; 2MB onboard video memory
The standard VGA driver is the most recent driver, and in fact the only one available for this hardware.
Labview 5.1 runs without problem on this machine, but when I loaded Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error, line 4150" every time I tried adding a graph to the front panel. Changing the screen acceleration properties did not make any difference.
Though I have gone back to version 5.1
for the time being, my application would benefit substantially from the current version.
Are there any fixes for this, or is Labview 6 simply not compatible with VGA screen drivers?
Thanks,
Jo

I have LV6.0.2 running on an Arcom SBC with the Chips and Technology 69000
HiQVideo 2MB display chip. This chip is not capable of rendering 3D graphics.
I have noticed the CPU will go to 100% usage if I open a sub-VI panel with lots
of the new 3D graphics on it, as the display chip passes rendering off to the
main processor.
Perhaps you could try replacing the LV6 3D graphics with the older versions
that are available on the Controls pallet. At 16 colors the new graphics look
terrible anyway.
I am running the chip at 1024 X 768 screen resolution and 65K colors with
no other problems.
Regards,
Alan Brause
"Jo" wrote in message news:[email protected]..
> I have an industrial PC with the following characteristics:
>
> * Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours
> only option)
>
> * ROBO 608, Industrial SBC motherboard with onboard video driver,
> from Chips and Technologies, 69000; 2MB onboard video memory
>
> The standard VGA driver is the most recent driver, and in fact the
> only one available for this hardware.
>
> Labview 5.1 runs without problem on this machine, but when I loaded
> Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error,
> line 4150" every time I tried adding a graph to the front panel.
> Changing the screen acceleration properties did not make any
> difference.
>
> Though I have gone back to version 5.1 for the time being, my
> application would benefit substantially from the current version.
>
> Are there any fixes for this, or is Labview 6 simply not compatible
> with VGA screen drivers?
>
> Thanks,
> Jo

Failure: "image.cpp", error 11602

I'm developing an application in LabView and with the Web publishing tool I can visualizethe results in Internet. The problem is that I open the explorer (Netscape or Internet Explorer) the following message appears in the screen: "Failure, "image.cpp", error 11602, please contact with NI" and the explorer is close... It's labview 6.1

eddie wrote:
>
> I'm developing an application in LabView and with the Web publishing
> tool I can visualizethe results in Internet. The problem is that I
> open the explorer (Netscape or Internet Explorer) the following
> message appears in the screen: "Failure, "image.cpp", error 11602,
> please contact with NI" and the explorer is close... It's labview 6.1
A good general starting point is www.ni.com/failure . Worth looking at
the specific tips (if any) for this error, and the general tips.
Mark

Getting CURL.cpp - Error?

Hi,
I updated to Mountain Lion and when using a audio converter, Sound Grinder 3.4.4, I get an error that reads as follows:
CURL.cpp - error "No URL" when getting Full Path, in getFolderFullPathAs CString0, line: 248
Can't find any thing regarding it so if someone can enlighten me of what this is and if there is a way to fix it I would appreciate it.
Thanks!

Funny I posted this and bang I figured it out. Seems Apple is getting as bad as PC's with their convoluted errors that make zero sense. Basically Sound Grinder's path to save a file, which was set in the preferences, was deleted by the new install. So once I told it where to save it was fine.
Thanks for the quick reply by the way!

Image.cpp error

When I try to print the labview panel & diagram on my new canpn pixma iP1000 printer I get the following message. I am using LV6.0
"image.cpp error" in line 11035. Please contact ni.com. Anyone can help!

hi labview 1958,
please look here:
Failure: image.cpp, line 11035 in LabVIEW 6.0
Greets!

Fpsane.cpp error

Hello,
Following an fpsane.cpp error, all open vi's crash and when they are reloaded they are temporarily reloaded in mandarin chinese. After a minute or so the language reverts back to english. Has anyone ever seen an error like this before?
Thanks,
Chase
Test Engineer - Subzero Freezer

1984 is most likely correct about the corrupt files. The fpsane.cpp error usually indicates something has become "very corrupted" as listed in the explanation of the error:
http://digital.ni.com/public.nsf/allkb/AFA28DCC3DE89839862566B200594E8C
Have you located the origin of the error?
Applications Engineer
National Instruments

CPP error line 638

Hi I'm having problems with the CPP ERROR at line 638, my application includes profibus and vision. In the past when I had CPP ERRORS I had found if I sequenced the profibus VI this would eliminate the problem, however the problem has returned. I thought maybe it would be the IMAQ for the vision, so I bypassed the vision altogether, it is still in the code but not currently called or used. This hasn't helped either, I was wondering if the issue could be with too many VI's running at the same time, perhaps a memory allocation problem, but I don't know at this point.
This has been most frustrating I'm running out of I deals
Thanks
Jeffery Orn

Hello Colorado,
Normally when you are starting up LabVIEW after a crash or another error happens, LabVIEW will give you the cpp file name and the line number. You then have the option to investigate the error. This will send a report to NI so that we can work on finding why the error happens and what we can do to fix it. You should probably send that error to NI if you have not done so already.
Since the cpp file and the version of LabVIEW is missing from you post, you may want to include it. It would probably be helpful to others who may have run into this error.
I hope this helps.
Steven T.

I am gettign objheap.cpp error

i had a cluster ( pretty large one ), i added few more controls to the cluster. when i tried to open the main vi where this custer is a contol in the FP, further the cluster is used for processing(updating , reading etc)in the code.
When i try to open the main vi with the modified cluster i get objheap.cpp error and the labview closes by itself when i press ok. What could be the reason for this problem.
Is there any precaution i need ahere to when working with large clusters.

Did you get a line number? That would go a long way to finding the reason for the error.
I believe that your VI has become corrupted due to the number of controls on your front panel. Not counting the controls in the clusters, how many objects do you have?
The following link points to another link that discusses the interal errors of LabVIEW. It might help.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000007510000&ECategory=LabVIEW.Datalogging+and+Supervisory+Control

How do I stop .cpp errors on opening firefox

when I open firefox I get a series of message boxes as follows:
353 regWithoutKeyname.cpp
49 dfxpRecord.cpp
234 dfxpInit.cpp
65 dfxpUniversal.cpp
86 winmmDfx.cpp
The number is the title of the box and the text is the file name. An OK button appears in each box and once pressed the next box appears.
How do I stop this from occurring ?

'''How to stop Firefox startup .cpp error dialog windows''':
* 353 ..\..\UTIL\reg\regWithoutKeyname.cpp
* 49 .\dfxp\dfxpRecord.cpp
* 234 .\dfxp\dfxpInit.cpp
* 65 \dfxp\dfxpUniversal.cpp
* 86 .\winmmDfx.cpp
'''It has nothing to do really with Firefox or plug-ins!'''
It happens in safe-mode as well. I also experienced the same problem in IE.
'''It is an Audio related problem'''
To my astonishment I could not find an answer anywhere until I realized that once upon a time I had installed DFX Audio Enhancer!
'''You have most likely [http://www.fxsound.com/index.php?vendor=23&subvendor=1&plus=2&refer=dfx11 DFX Audio Enhancer] installed''' and corrupted. Possibly due to a a deep registry clean scan which removed some keys.
'''''Simply reinstall DFX Audio Enhancer and you problem is solved!'''''
Fire fox error messages

Compiling COBOLs in PSOVM - psrun.mak error - "cob64: can not execute Id".

Hi All,
After installing PeopleSoft OVM in our server, I need to recompile the COBOL. I believe this is not included in the OVM. These are the steps I did.
1. Installed Microfocus Server Express 5.0 WrapPack 4
2. Follow the steps in Compiling Cobol in Unix mentioned is the PeopleTools_8.50_Installation_Oracle guide.
I was able to successfully compille the COBOL files by running ./pscbl.mak. The next step is Linking COBOL Components on UNIX by running ./psrun.mak and here I got the error:
+./psrun.mak - linking PSRUN for oel-5-x86_64, Version 2.6.18-92.0.0.0.1.el5xen ...+
+./psrun.mak - Error(s) encountered creating PSRUN!+
+./psrun.mak - See /opt/oracle/psft/appbatch/tools/setup/psrun.err for messages+
+[root@pshcm91ab setup]# more /opt/oracle/psft/appbatch/tools/setup/psrun.err+
cob64: can not execute ld
+[root@pshcm91ab setup]#+
I followed all the steps in setting environment variable mention in the "Compiling Cobols in Unix" in PeopleTools_8.50_Installation_Oracle.
Is there any specific documentation of compiling COBOLs in PeopleSoft OVM?
Can anyone help me with this?
Thanks in advance.
-Chris
Edited by: user9977167 on 4/02/2010 15:52
Edited by: user9977167 on 5/02/2010 06:18

Hi,
Ok, I reproduce your case :
[psadm1@psovmab setup]$ ./psrun.mak
./psrun.mak - linking PSRUN for oel-5-x86_64, Version 2.6.18-92.0.0.0.1.el5xen ...
./psrun.mak - Error(s) encountered creating PSRUN!
./psrun.mak - See /opt/oracle/psft/appbatch/tools/setup/psrun.err for messages
[psadm1@psovmab setup]$ more /opt/oracle/psft/appbatch/tools/setup/psrun.err
cob64: can not execute ld
[psadm1@psovmab setup]$It looks like a lot of rpm packages required by ld are missing on Peoplesoft OVM App/Batch server compared to the Peoplesoft OVM database server for instance.
I added a lot of packages because of the dependendcies as below :
From OEL5.2 Disk 1
==================
-rw-r--r-- 1 root root 899210 Feb 7 10:10 kernel-headers-2.6.18-92.el5.x86_64.rpm
-rw-r--r-- 1 root root 3073639 Feb 7 10:25 binutils-2.17.50.0.6-6.el5.x86_64.rpm
-rw-r--r-- 1 root root 3114462 Feb 7 10:29 cpp-4.1.2-42.el5.x86_64.rpm
[root@psovmab rpm]# rpm -Uvh kernel-headers-2.6.18-92.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:kernel-headers         ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh binutils-2.17.50.0.6-6.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:binutils               ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh cpp-4.1.2-42.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:cpp                    ########################################### [100%]
[root@psovmab rpm]#
From OEL5.2 Disk 2
==================
-rw-r--r-- 1 root root 614718 Feb 7 10:05 glibc-headers-2.5-24.x86_64.rpm
-rw-r--r-- 1 root root 2535024 Feb 7 10:05 glibc-devel-2.5-24.x86_64.rpm
-rw-r--r-- 1 root root 2105297 Feb 7 10:05 glibc-devel-2.5-24.i386.rpm
-rw-r--r-- 1 root root 5544086 Feb 7 10:20 gcc-4.1.2-42.el5.x86_64.rpm
-rw-r--r-- 1 root root 3987493 Feb 7 10:20 gcc-c++-4.1.2-42.el5.x86_64.rpm
-rw-r--r-- 1 root root    83518 Feb 7 10:31 libgomp-4.1.2-42.el5.i386.rpm
-rw-r--r-- 1 root root    84654 Feb 7 10:41 libgomp-4.1.2-42.el5.x86_64.rpm
-rw-r--r-- 1 root root 2980440 Feb 7 10:43 libstdc++-devel-4.1.2-42.el5.x86_64.rpm
-rw-r--r-- 1 root root    20483 Feb 7 11:46 elfutils-libelf-devel-0.125-3.el5.x86_64.rpm
-rw-r--r-- 1 root root    58852 Feb 7 11:46 elfutils-libelf-devel-static-0.125-3.el5.x86_64.rpm
-rw-r--r-- 1 root root   102193 Feb 7 11:49 elfutils-libs-0.125-3.el5.x86_64.rpm
[root@psovmab rpm]# rpm -Uvh glibc-headers-2.5-24.x86_64.rpm
Preparing...                ########################################### [100%]
   1:glibc-headers          ########################################### [100%]
[root@psovmab rpm]#
[root@psovmab rpm]# rpm -Uvh glibc-devel-2.5-24.x86_64.rpm
Preparing...                ########################################### [100%]
   1:glibc-devel            ########################################### [100%]
[root@psovmab rpm]#
[root@psovmab rpm]# rpm -Uvh glibc-devel-2.5-24.i386.rpm
Preparing...                ########################################### [100%]
   1:glibc-devel            ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh libgomp-4.1.2-42.el5.i386.rpm
Preparing...                ########################################### [100%]
   1:libgomp                ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh libgomp-4.1.2-42.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:libgomp                ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh gcc-4.1.2-42.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:gcc                    ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh libstdc++-devel-4.1.2-42.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:libstdc++-devel        ########################################### [100%]
[root@psovmab rpm]#
[root@psovmab rpm]# rpm -Uvh gcc-c++-4.1.2-42.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:gcc-c++                ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh elfutils-libs-0.125-3.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:elfutils-libs          ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh elfutils-libelf-devel-0.125-3.el5.x86_64.rpm elfutils-libelf-devel-static-0.125-3.el5.x86_64.rpm
Preparing...                ########################################### [100%]
   1:elfutils-libelf-devel-s########################################### [ 50%]
   2:elfutils-libelf-devel ########################################### [100%]
[root@psovmab rpm]#
From OEL5.2 Disk 3
==================
-rw-r--r-- 1 root root 4588773 Feb 7 10:22 compat-gcc-34-3.4.6-4.x86_64.rpm
-rw-r--r-- 1 root root 13542100 Feb 7 10:23 compat-gcc-34-c++-3.4.6-4.x86_64.rpm
-rw-r--r-- 1 root root   232846 Feb 7 12:21 compat-libstdc++-33-3.2.3-61.x86_64.rpm
[root@psovmab rpm]# rpm -Uvh compat-gcc-34-3.4.6-4.x86_64.rpm
Preparing...                ########################################### [100%]
   1:compat-gcc-34          ########################################### [100%]
[root@psovmab rpm]# rpm -Uvh compat-gcc-34-c++-3.4.6-4.x86_64.rpm
Preparing...                ########################################### [100%]
   1:compat-gcc-34-c++      ########################################### [100%]
[root@psovmab rpm]#The initial error is gone, but got a new one when linking :
[psadm1@psovmab setup]$ ./psrun.mak
./psrun.mak - linking PSRUN for oel-5-x86_64, Version 2.6.18-92.0.0.0.1.el5xen ...
./psrun.mak - Error(s) encountered creating PSRUN!
./psrun.mak - See /opt/oracle/psft/appbatch/tools/setup/psrun.err for messages
[psadm1@psovmab setup]$ more /opt/oracle/psft/appbatch/tools/setup/psrun.err
ld: cannot find -lgcc
[psadm1@psovmab setup]$I looked around for this error, found a Metalink note, but the suggestion does not apply here, the path directory metioned in $COBDIR/etc/cobopt already exists :
[psadm1@psovmab setup]$ more $COBDIR/etc/cobopt
-C nolist
set GCC_LIB=/usr/lib/gcc/x86_64-redhat-linux/3.4.6
[psadm1@psovmab setup]$ ls /usr/lib/gcc/x86_64-redhat-linux/3.4.6
32          crtbeginS.o crtend.o   include   libgcc_eh.a libgcc_s_32.so libstdc++.a   libstdc++_nonshared.a libsupc++.a
crtbegin.o crtbeginT.o crtendS.o libgcc.a libgcc_s.so libgcov.a       libstdc++.so libstdc++_shared.so    specs
[psadm1@psovmab setup]$So far, no luck, I'll still try, but you may have more luck to install a separate server with all the packages install from the scratch and run a process scheduler from there.
Nicolas.

Lvinit.cpp error

I've installed NI-VISA and Labview using kernel 2.6.18 and each time I launch Labview the splash window appears for a second or so, then the application craches with the error message:
Fatal Internal Error : "lvinit.cpp", line 1553
LabVIEW version 8.2.1
this happens with both root and normal user. I looked for the lvinit.ccp file but it doesn't even exist in my box.
Any help?
thanks in advance,
G.

Hi Giuseppe,
thanks for the hint. Now it works again.
I summarised what I've done for future reference.
I've downloaded a 2.6.16 kernel, compiled and booted.
then I've installed NI-VISA packages with
alien --scripts <package>.rpm
dpkg -i <package>.deb
in the order listed in the NI-VISA INSTALL script
once done I launched updateNIDrives (don't know if was necessary)
then I've done the same for labview 8.2.1 packages
next: I'll try to install NI-488 and NI-DAQ
G.

SUKeyCompare.cpp Error in OBIEE 11g

Hi All,
I am getting the below error for one of the report.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46008] Internal error: File server\Utility\Server\DataType\SUKeyCompare.cpp, line 880. (HY000)
If anyone has any clue, please let me know.
Thanks,
Soumitro

What is in report, any calculations?
I would say narrow down to a particular column, just delete a measure and execute the report if runs add it back and delete another etc.
Give some more info about the background of the report interms column expressions etc.

The compilation failed due to a Xilinx error (410)

Hi Peeps,
I'm trying to compile my FPGA code with the Cloud Compile Service. I have an FPGA code that compiles without any problems. When I put a DMA FIFO Node into this code, I get the following Xilinx compiler error:
ERROR:HDLCompiler:410 - "/opt/apps/NIFPGA/jobs/CSD2awO_GQdD63p/NiFpgaAG_0000050c_CaseStructureFrame_0001.vhd" Line 211: Expression has 66 elements ; expected 50
Netlist NiFpgaAG_0000050c_CaseStructureFrame_0001(vhdl_labview) remains a blackbox, due to errors in its contents
The code compiles well without the DMA Node. The DMA is a Target to Host DMA, 1023 element long (Block Memory), the type of the elements is U32.
There are other thing on the block diagram as well. When I copy this SCTL into a new VI without anything else in it, it compiles without problems, regardless if the DMA Node is there.
Please find the VI snippet and the error summary attached.
Any ideas are welcome.
Cheers,
Norbert
Solved!
Go to Solution.
Attachments:
FPGA.png ‏92 KB
Error Report.txt ‏36 KB

So the problem seems to be resolved...
I deleted the DMA FIFO node from the block diagram and added it again. After about 40 minutes I had a successful compilation. Weird.

Linker.cpp error @ line 2075 w/Labview 6.0.2 and Appl. Builder

So frustrating! The libraries run in the debugging environment just fine. No errors and two minor warnings. I have to constantly tweak and upgrade these libraries because each has about 40 VIs and are rebuilt on average two times a week. The executables are used at a dozen places and I can't place the developer system on each computer, that is what the Builder and the Labview runtime engine is for.
About a month ago after doing very minor changes in one VI I rebuilt the library into an executable using the same build file and BANG, I get this linker error. After acknowledging Labview disappears (stealth crash). Well eventually I figured I had to copy the diagram of the VI I had changed (yes, complete with changes) to another blank VI. After deleting the old VI and renaming the new (it used to be blank) VI, I rebuilt it. Everything was fine.
Well I have tried to rebuild frequently after each change and save often several copies back a month but somehow this has been futile as the error is back in both libraries. In the two libraries I maintain there are as many as 20 VIs identical between the two libraries. I make a change in one VI in one of the libraries then use the library manager to copy it to the other library. This has worked hundreds of times over the last year and half. Well somehow the problem has come back in both libraries and I can't isolate the bad VI.
Obviously one (or maybe more!) of the VIs are put together wrong but Labview doesn't detect it. I don't use any fancy linking to anything other than DAQ and SERP drivers, everything else are simple VIs (just Labview code) with only the Labview supplied VIs talking to DLLs. I have tried my little cut and paste trick with the last few changed VIs but it didn't work. I tried to use Application Builder to build VIs seperately but that was useless. I tried elminating the lastest changed VIs from the library and rebuilding but to no avail. It fails approximately 1/4 to 1/3 into the build process bar indicator but the Builder doesn't say what file it is building so I can't relate it to any specific VI. Tried relating the bar position to a latest changed list and an alphabetical list but that was inconclusive.
This issue is currently being worked on by NI support but I want to try the resources of the developer community because this is such a rare problem with big implications (at least to me).

OK, NI support came through! If the library is mass compiled the typedef in my controls won't mess with the linker. Labview 6.1 solves this problem.
Since my email to NI support got returned I'm not sure they received it. The message is: it worked and thanks.

Compile XSLSample.c or XSLSample.cpp error

Similar Messages

Maybe you are looking for