Build error xsc

This forum is meant for questions and discussions about the X# language and tools
User avatar
SHirsch
Posts: 284
Joined: Tue Jan 30, 2018 8:23 am

Build error xsc

Post by SHirsch »

Hello,

When trying to compile exported VO code following errors and warning occur.
Error_XSC_2.PNG
Error_XSC_2.PNG (176.5 KiB) Viewed 432 times
Error_XSC_1.PNG
Error_XSC_1.PNG (14.54 KiB) Viewed 432 times
Same errors and warnings have been corrected in VO and exported again. As you can see no source file is given where these errors and warning comefrom.
How to solve this problem?
Compiler 1.1.1

Thanks for helping
Regards,
Stefan
User avatar
wriedmann
Posts: 3658
Joined: Mon Nov 02, 2015 5:07 pm
Location: Italy

Build error xsc

Post by wriedmann »

Hi Stefan,

maybe you have posted this to the wrong forum, because your question is about the X# compiler and not VO and Vulcan.

Let me see please if I understand your problem correctly: you have exported your VO application as AEF, and used the XPorter to create a new Visual Studio project.
Afterwards you have fixed these errors on the VO side, exported again to AEF and then re-executed the XPorter? And in Visual Studio the code of the first version showed up?

If this is true, please double check that you used the correct AEFs as XPorter source and that you have used the correct destination path in the XPorter.

Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
User avatar
SHirsch
Posts: 284
Joined: Tue Jan 30, 2018 8:23 am

Build error xsc

Post by SHirsch »

Hi Wolfgang,

your description is correct.

I checked the AEF and saved the output of VOXPorter to a secondary folder.
Attached a screenshot of the next AEF where you can see both messages. The same appeared with the first AEF. After correcting all errors and warnings with a source file given, the errors with XSC as file still remain.
Error_XSC_3.PNG
Error_XSC_3.PNG (63.72 KiB) Viewed 432 times
Stefan
(Is it possible the move to correct forum?)
User avatar
wriedmann
Posts: 3658
Joined: Mon Nov 02, 2015 5:07 pm
Location: Italy

Build error xsc

Post by wriedmann »

Hi Stefan,

(unfortunately I'm not an administrator and therefore I cannot move the thread, but maybe Chris or Robert will do it later).

The errors you posted now (they are are hard to read from the image) seem to leed to missing dependencies.
Do you have Vulcan.NET installed on your machine? Please doublecheck the dependencies of your project - they should include the the various VulcanVO*.dll files.
If you have no Vulcan installed, they are not in the GAC, and you need to point to the correct location.
Please make sure that you don't overwrite your project files when using Xporter more than once (fortunately there is such an option). Otherwise the XPorter will overwrite your changes to the dependencies and other changes in the Visual Studio project.

Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
User avatar
SHirsch
Posts: 284
Joined: Tue Jan 30, 2018 8:23 am

Build error xsc

Post by SHirsch »

Hi Wolfgang,

I referenced Grafx.Classmate.Base, ..Functions, ..Gui, ..Interface, mscorlib, SDK_DEFINES, System, System.Code, VulcanRT, VulcanRTFuncs, VulcanVOSystemClasses and VulcanVOWin32APILibrary.
Vulcan is Version 2.1.212 (the last one I had access to)
The references for Classmate I had compiled successfully with X# yesterday.

I think more than these libraries are not necessary.

Any other ideas?

Stefan
User avatar
wriedmann
Posts: 3658
Joined: Mon Nov 02, 2015 5:07 pm
Location: Italy

Build error xsc

Post by wriedmann »

Hi Stefan,

unfortunately I have no idea about ClassMate: could it be that there is another namespace than Vulcan.VO?

If yes, you should add a "using" statement at the top of your prg file.

Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
User avatar
robert
Posts: 4279
Joined: Fri Aug 21, 2015 10:57 am
Location: Netherlands

Build error xsc

Post by robert »

Stefan,
Stefan Hirsch wrote: (Is it possible the move to correct forum?)
I have moved the thread to the correct forum.
To answer your other questions I need to see your code and the full text of the error message. The screen dumps do not have enough info.

Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
User avatar
SHirsch
Posts: 284
Joined: Tue Jan 30, 2018 8:23 am

Build error xsc

Post by SHirsch »

Hi Wolfgang,

I don't think it has to do with namespaces. Here the error for better readablity again:

Schweregrad: Fehler
Code: XS1503
Beschreibung: Argument 2: cannot convert from 'dword' to 'word'
Projekt: 10_kdBase10_1016
Datei: XSC
Zeile: 1

same message from output window:
XSC(1,12379): error XS1503: Argument 2: cannot convert from 'dword' to 'word'

Normally in column 'Datei' is the source file and in 'Zeile' the line of the error. Here is XSC as source file with line 1 as position of the error.

What does 12379 mean? Is there an temporary file that I can look into? May there is some more information available.


Stefan
User avatar
wriedmann
Posts: 3658
Joined: Mon Nov 02, 2015 5:07 pm
Location: Italy

Build error xsc

Post by wriedmann »

Hi Stefan,

in the last image you had posted I had seen errors like "The type or namespace could not be found" - therefore my idea about namespaces.
This explains maybe why I don't like images from error messages at all: a copy of the text is much easier to read (and makes it possible for Google to index the message for subsequent searchers too).

But now Robert can take over - my knowledge is too limited, unfortunately.

Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
User avatar
SHirsch
Posts: 284
Joined: Tue Jan 30, 2018 8:23 am

Build error xsc

Post by SHirsch »

Hi Wolfgang,

you are right. In this screenshot my focus was on column 'Datei' and not the error message. I tried to show the difference between the messages. These namespace errors are explainable and correctable (came from another library that depends on the current problematic one).

Regards,
Stefan
Post Reply