Compilation error: lnk2534 (with VP 7.5)
Hello,
A try convert my project in VIP7.0 to my new VIP7.5.
and i have this error 2534 when i compil.
Can you help me please ?
Thank you
A try convert my project in VIP7.0 to my new VIP7.5.
and i have this error 2534 when i compil.
Can you help me please ?
Thank you
- Attachments
-
- compilVIP.JPG (122.43 KiB) Viewed 17190 times
Daniel Perraud
-
- VIP Member
- Posts: 331
- Joined: 14 Nov 2002 0:01
-
- VIP Member
- Posts: 331
- Joined: 14 Nov 2002 0:01
There are detailed infos in the Upgrade Notes of the Release Notes. Supposably they can help you in the upgrade.
Regards Martin
Thank you Martin,
I had read the notes on the updates, and I had to re-write the 'findall' and 'trap'.
I tried to recompile after deleting the temporary files, but I have the same error message.
Below the link to retrieve my project. (CAAGL.ZIP 413 Ko, project is project: CAAGL.vipprj)
https://1drv.ms/u/s!AuypDPPFdHXshSS6O6RfnEorUo-v
Can you tell me if you also get this error message?
Thank you for your help.
I had read the notes on the updates, and I had to re-write the 'findall' and 'trap'.
I tried to recompile after deleting the temporary files, but I have the same error message.
Below the link to retrieve my project. (CAAGL.ZIP 413 Ko, project is project: CAAGL.vipprj)
https://1drv.ms/u/s!AuypDPPFdHXshSS6O6RfnEorUo-v
Can you tell me if you also get this error message?
Thank you for your help.
Daniel Perraud
-
- VIP Member
- Posts: 331
- Joined: 14 Nov 2002 0:01
-
- VIP Member
- Posts: 331
- Joined: 14 Nov 2002 0:01
My attempt to fit your code into a project hull generated by VIP7.5.0.2:
https://1drv.ms/u/s!AinVXVo575qdkSVRQ6ILxoBHwWKN
https://1drv.ms/u/s!AinVXVo575qdkSVRQ6ILxoBHwWKN
Regards Martin
- Thomas Linder Puls
- VIP Member
- Posts: 1424
- Joined: 28 Feb 2000 0:01
I am not quite sure why you get that error message.
But either you should remove the #export directive in caagl.pro or remove the caagl.def file from the project.
Using #export and a def file are two alternative ways of specifying the exports (#export is the "modern" way, so I think you should remove the def file).
Bu the way, I would restructure the project into mode packages have each package in a separate directory (as like Martin Meyer does in his reconstruction of your project, just in even more packages).
But either you should remove the #export directive in caagl.pro or remove the caagl.def file from the project.
Using #export and a def file are two alternative ways of specifying the exports (#export is the "modern" way, so I think you should remove the def file).
Bu the way, I would restructure the project into mode packages have each package in a separate directory (as like Martin Meyer does in his reconstruction of your project, just in even more packages).
Regards Thomas Linder Puls
PDC
PDC
Happy new year 2017 !
Thank you fors your answers, i now get my dll.
bud it does not work.
This is because of the list structures that have to change with the V7.5. (it seems to me)
My VIP dll is plugged into a Delphi program.
I pass Delphi variables 'string_list 'and 'integer_list'
These types are described like this in Delphi:
type
PChaineliste = ^listString;
listString = record
functor: byte;
value: PWideChar;
next: PChaineliste;
end;
PIntegerListe = ^listInteger;
listInteger = record
functor: byte;
value: integer;
next: PIntegerliste;
end;
Can you tell me how to describe now these 2 types prolog in Delphi?
Thank you.
Thank you fors your answers, i now get my dll.
bud it does not work.
This is because of the list structures that have to change with the V7.5. (it seems to me)
My VIP dll is plugged into a Delphi program.
I pass Delphi variables 'string_list 'and 'integer_list'
These types are described like this in Delphi:
type
PChaineliste = ^listString;
listString = record
functor: byte;
value: PWideChar;
next: PChaineliste;
end;
PIntegerListe = ^listInteger;
listInteger = record
functor: byte;
value: integer;
next: PIntegerliste;
end;
Can you tell me how to describe now these 2 types prolog in Delphi?
Thank you.
Daniel Perraud
- Thomas Linder Puls
- VIP Member
- Posts: 1424
- Joined: 28 Feb 2000 0:01
ok thank you, it's clear.
The notion of 'nil' must be different in Visual Prolog and Delphi
The test on the pointer to nil in Delphi like this: P=nil does not work.
With this fonction, it seems to work:
function isnil(const p: Pointer): Boolean;
begin
Result:= dword(addr(p^))=1;
end;
Do you think the function is well written ?
thank you.
The notion of 'nil' must be different in Visual Prolog and Delphi
The test on the pointer to nil in Delphi like this: P=nil does not work.
With this fonction, it seems to work:
function isnil(const p: Pointer): Boolean;
begin
Result:= dword(addr(p^))=1;
end;
Do you think the function is well written ?
thank you.
Daniel Perraud
- Thomas Linder Puls
- VIP Member
- Posts: 1424
- Joined: 28 Feb 2000 0:01
You are right the empty list it is not a null pointer but a pointer that has the value 1.
The implementation of the function looks correct, but I think would create it on the list types:
<pre>function isEmpty_integerList(const p: PIntegerListe): Boolean;
begin
Result := dword(addr(p^))=1;
end;</pre>
The implementation of the function looks correct, but I think would create it on the list types:
<pre>function isEmpty_integerList(const p: PIntegerListe): Boolean;
begin
Result := dword(addr(p^))=1;
end;</pre>
Regards Thomas Linder Puls
PDC
PDC
- Thomas Linder Puls
- VIP Member
- Posts: 1424
- Joined: 28 Feb 2000 0:01