|
I wouldn't know. I don't have enough fingers to count that high 
|
|
|
|
|
Fingers n toes. Then all you need is something to serve as bit 21.. 
|
|
|
|
|
Probably part of the reason is their compiler has gone through quite an evolution since then. I don't even think it's the same codebase - as in it has been rewritten at least once.
It used to be their compiler wasn't standard enough to implement the STL properly. That was in the bad old days of 6.
So bet on having to change your code in places. It's no so easy for an automagic tool to rewrite C++.
Real programmers use butterflies
|
|
|
|
|
That's because you're trying to convert a project written by a 1998 tool with a 2018 one. Precompiled headers management changed (luckily, as it was plain dumb in VC6) and mostly the standard changed, I had to add many casts when using floor and ceil because they are handled differently, otherwise it faild compilation.
Who knows if a project written for GCC 2.8.1 compiles with GCC 11.2 (and the accompanying libc versions).
Converting code is never, ever a click-boom task.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
den2k88 wrote: Converting code is never, ever a click-boom task.
Good choice of words here. It probably does go "boom" in this case...
|
|
|
|
|
Having been on both sides of the fence multiple times my choice was not random at all.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I understand that compilers change. I know how to handle the source code issues.
My argument is that if Microsoft converts the project, there should be sufficient intelligence in the conversion process to ascertain what SDKs are on the machine, what tool is being used, and make some sort of attempt at setting up Microsoft's own definitions. What I get is some cryptic compiler error that seems to be obvious but difficult to resolve.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
charlieg wrote: there should be sufficient intelligence in the conversion process to ascertain what SDKs are on the machine, what tool is being used, and make some sort of attempt at setting up Microsoft's own definitions.
Whenever you translate code you don't change the original code, ever, this includes setting definitions that opaquely modify the code itself. This is a golden rule of each, any and every transcompiler. Jumping 20 years in technology cannot be automated, and that's true in all fields.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
charlieg wrote: My argument is that if Microsoft converts the project, there should be sufficient intelligence in the conversion process to ascertain what SDKs are on the machine, what tool is being used,
I'd love to see that working.
I've seen projects that were poorly documented, and new hires couldn't figure out how to build them. I don't see how any such thing could ever be automated.
Personally I think whenever a new project is started, there should be some sort of formal documentation that describes the system used, the tools used, their version number, any command that was run from a command prompt (if involved the configuration) and heck, even a copy of each tool's own installer, since you can't rely on a URL to remain valid across time.
|
|
|
|
|
charlieg wrote: I have *never* had a project convert and then compile
That just might be a step too far. I think there have been 9 major releases of Visual Studio since VC6: Visual Studio .NET 2003, and then Visual Studio 2005, 2008, 2010, 2013, 2015, 2017, 2019, and now 2022. Considering the phenomenal changes in the languages, runtimes, and operating system in that time, this devolves down to the dancing bear: you don't compliment him on the grace of his en pointe.
We just converted a large-ish code base (8 solutions, 30+ projects, C++/MFC and C#/WPF, several hundred source files totalling 3 million lines of code or so) from building with Visual Studio 2008 to Visual Studio 2019. Everything compiled and more-or-less ran. Two of us spent about a week cleaning up new warnings produced by improved compiler diagnostics, only one of which was genuinely annoying.
Software Zen: delete this;
|
|
|
|
|
Probably. I'd be okay with basic issues. But *Microsoft* is the one releasing this stuff, and it's like there is zero coordination going on. Hmmm, maybe instead of bitching I'll figure it all out and write an article. 
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Well to wrap this issue up, I still am willing to call Microsoft clowns. This issue is just too easy to avoid. I'm sure I missed it in the documentation somewhere....
My original premise is that this was a VC6 application. Apparently, someone ported it years back to VS2015. So, not too old.
Anyway, MFC from the beginning (I'm going a long ways back, so I might be wrong), Microsoft's approach was to generate a stdafx.h and .cpp file that pulled in the MFC and Win32 definitions and what have you. If you were using something special for your application, you typically added it to stdafx.h.
Fast forward to sometime later (I don't know when MS decided to change the approach, I'd have to start downloading each VS to see how it behaved). Creating the dummy mfc app and staring at it for a while, I noticed there is no stdafx.* files. Instead, the newer versions of VS use a framework.h including a targetver.h - framework.h seems (I have a small test set admittedly) to be included in all of my application files. Within targetver.h, we include SDKDDKVer.h which is the magic file that fixes everything.
I would argue that the conversion report should include some sort of message about this.
Documented for posterity.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I do not have to compile or debug the code on Mac - only to run it.
Thanks
Nick Polyak
|
|
|
|
|
I'm somewhat confused. What is a 'remote MacOS desktops'.
Is setting up a virtual Mac too naive to solve this?
|
|
|
|
|
Virtual Mac would be great also. I just do not know how to do it or where to buy it. There are plenty of instructions for setting up a virtual Linux machine - which I did, but I could not find good instructions for Mac.
Nick Polyak
modified 15-Dec-21 14:39pm.
|
|
|
|
|
|
The problem is I want to get the BigSur.iso from a reliable place (e.g. apple) and apple does not seem to allow me to download it on windows.
Nick Polyak
|
|
|
|
|
If you private message me, I can give you some hints.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I do not see how I can private message you from the codeproject site, unfortunately. If you want connect to me on linkedin (I provide a link next to my profile) and there we'll be able to exchange the messages or you'll be able to see my e-mail address.
Nick Polyak
|
|
|
|
|
VM on non-Apple hardware?
Difficult, illegal, but not impossible. The Apple Eula disallows installing Mac OS on non-Apple hardware. There are sites that provide instructions though.
>64
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
|
It is very easy, but I want some solutions preferably tested by others. Perhaps this is not the best forum for Mac OS
Nick Polyak
|
|
|
|
|
I'm sending this from my Hackintosh. I think that's what they call it.
I don't feel bad, because I have a Mac-mini sitting on my desk. It works like a champ. I run it under VMWare Workstation Professional, but I know it runs elsewhere.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
|
These bastards refuse to upgrade my dotnet runtime. I am looking for someone instead of them.
Nick Polyak
modified 16-Dec-21 12:01pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
