Hi
any chances of removing the win32.mak dependency?
It would simplify the process.
All the best
Marco
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Mon, Dec 6, 2021 at 06:11 AM, Bob Bolch wrote:
The GCCCMS userID contains the compiler install materials, and there is nothing there that?
an ordinary compiler user needs. Any changes made on that ID could impact the ability to
regenerate the compiler. Everything you need to use the compiler is made available by the GCC?
EXEC. The GCC EXEC also uses runtime libraries made for CMS that are maintained on
the MAINTC ID. Please elaborate?on why you are logging on to GCCCMS. Maybe we can
simplify the method you are using.
I was looking for the equivalent of /usr/include/*.h and /usr/include/sys/*.h? files, so I can build the Zlib program library, the basis for zip and unzip. I wasn't logging on to GCCCMS, but using the MDISK entries from USER DIRECT to see what GCCCMS had. In the process of searching, I happened to look for all the copies of GCC EXEC and thought I noticed a discrepancy. :-D I have yet to read through the GCC EXEC S, code. So much to do, and so little time, but I have a need to know what header files are available for a compile, so of all the places I could pick, I started with GCCCMS and its minidisks. I didn't know about MAINTC, so I will also look there. I don't consider myself just a compiler user, since I have written and installed applications, for "general users" over the years for both VM/* and for *nix. I also don't consider myself an expert, more of the "Jack of all trades, master of none" sort. Thank you very much for the pointers. ?... Mark S.
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Hi Mark,
The GCCCMS userID contains the compiler install materials, and there is nothing there that? an ordinary compiler user needs. Any changes made on that ID could impact the ability to regenerate the compiler. Everything you need to use the compiler is made available by the GCC? EXEC. The GCC EXEC also uses runtime libraries made for CMS that are maintained on the MAINTC ID. Please elaborate?on why you are logging on to GCCCMS. Maybe we can simplify the method you are using.
Best regards, Bob
Mark, ? Probably because GCC EXEC on GCCCMS is the one Paul supplies with the base GCC. He knows nothing of GCCLIB so it would probably get in the way of his build process. Possibly there should be a copy there, but I am not sure it works on the GCCCMS ID because of the way it links and accesses the include files. ? Dave ? ? This might be for Bob Bolch ...
I'm trying to understand too many things, but in any case I end up with the following question. Why does the GCC EXEC S not exist on the GCCCMS minidisks?
When I have the disks accessed as below. The bolded ones are all the GCCCMS minidisks.
Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total
XMAS91 191 A?? R/W?? 30 3350? 800???????? 18?????? 4051-24????? 13049????? 17100
MNT5E5 5E5 B/B R/O?? 30 3350? 800???????? 11??????? 119-01????? 16981????? 17100
GCC191 120 C?? R/W? 100 3350? 800????????? 7??????? 669-01????? 56331????? 57000
XMAS92 192 D?? R/W?? 30 3350? 800??????? 213?????? 7065-41????? 10035????? 17100
PDPCLB 121 E/C R/O?? 10 3350? 800???????? 17???????? 95-02?????? 5605?????? 5700
GCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700
GCC291 123 G/C R/O? 115 3350? 800???????? 32????? 12303-19????? 53228????? 65531
GCC391 124 H/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC491 125 I/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC591 126 J/C R/O?? 34 3350? 800???????? 84????? 13730-71?????? 5650????? 19380
GCC691 127 K/C R/O?? 45 3350? 800??????? 537????? 19340-75?????? 6310????? 25650
GCC791 128 L/C R/O?? 64 3350? 800??????? 184????? 23041-63????? 13439????? 36480
GCC891 129 M/C R/O?? 40 3350? 800??????? 120?????? 3607-16????? 19193????? 22800
MYTOOL 193 R/R R/O?? 30 3350? 800??????? 185?????? 1217-07????? 15883????? 17100
CMSDSK 190 S?? R/O?? 59 3350? 800??????? 172????? 19533-58????? 14097????? 33630
VMTOOL 196 T/S R/O?? 70 3350? 800???????? 29?????? 1860-05????? 38040????? 39900
MNT19D 19D U/S R/O?? 70 3350? 800??????? 397?????? 5296-13????? 34604????? 39900
MNT19E 19E Y/S R/O?? 70 3350? 800??????? 682????? 24651-62????? 15249????? 39900
Ready; T=0.01/0.01 03:16:01
When I look for all the GCC EXEC files, I get the following. Shouldn't The S-disk version also be on one of the GCCCMS minidisks?
l gcc exec * ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
GCC????? EXEC???? J1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? K1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? Y2? V??? 79??? 272???? 10? 08/03/10?? 19:53
Ready; T=0.01/0.01 03:28:34
Granted my minidisk layout doesn't match, by filemode, the files GCCCMS MEMO.
type gcccms memo c
?
Disk layout for GCCCMS userid February 2021
?
191 A - work disk
291 B - GCC compiler version 3.2.3 MVS 8.5 from 2011
391 C - currently empty
491 D - currently empty
591 E - GCC compiler version 3.2.3 MVS 7.0 from 2009
691 F - GCC & PDPCLIB from 2009? source only
791 G - S, C and H files associated with stuff on F disk?
891 H - GCCLIB version 1.3.1.
?
Ready; T=0.01/0.01 03:33:12
If the 291 minidisk, is the current, production minidisk for VM/370 CE, then should not a copy of GCC EXEC S be on that minidisk as well?
Yours in confusion,
?... Mark S.
|
Looks like attachments are off as well
Dave
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Fish Fish
Sent: 06 December 2021 09:29
To: [email protected]
Subject: Re: [h390-vm] Visual studio 2022
Peter wrote:
Fish wrote:
laddiehanus wrote:
I installed all the SDK¡¯s including the on for XP Did it look like this? [...]
I don¡¯t know what kind of picture you sent, but it did not come
through in email , nor on the groups.io website either (at least not
for me). (grumble) That's what I get for trying to send HTML email I guess (grumble)
Let me try attaching it instead.
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
Peter wrote: Fish wrote:
laddiehanus wrote:
I installed all the SDK¡¯s including the on for XP Did it look like this? [...] I don¡¯t know what kind of picture you sent, but it did not come
through in email , nor on the groups.io website either (at least
not for me). (grumble) That's what I get for trying to send HTML email I guess (grumble) Let me try attaching it instead. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
Fish, ? I don¡¯t know what kind of picture you sent, but it did not come through in email , nor on the groups.io website either (at least not for me). ? Peter ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Fish Fish Sent: Monday, December 6, 2021 12:48 AM To: [email protected]Subject: Re: [h390-vm] Visual studio 2022 ? laddiehanus wrote: ? > I installed all the SDK¡¯s including the on for XP ? Did it look like this? ?
? --
? ? ? ? ? "Fish"? (David B. Trout)
Software Development Laboratories
? ? ? ? ? ?
? ? ? ? ? ? ? ? fish@... ? ?
|
laddiehanus wrote: ? > I installed all the SDK¡¯s including the on for XP ? Did it look like this? ?
? --
? ? ? ? ? "Fish"? (David B. Trout)
Software Development Laboratories
? ? ? ? ? ?
? ? ? ? ? ? ? ? fish@... ? ?
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Mark, ? Probably because GCC EXEC on GCCCMS is the one Paul supplies with the base GCC. He knows nothing of GCCLIB so it would probably get in the way of his build process. Possibly there should be a copy there, but I am not sure it works on the GCCCMS ID because of the way it links and accesses the include files. ? Dave ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 06 December 2021 03:40
To: [email protected]
Subject: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk? #VMCE? This might be for Bob Bolch ...
I'm trying to understand too many things, but in any case I end up with the following question. Why does the GCC EXEC S not exist on the GCCCMS minidisks?
When I have the disks accessed as below. The bolded ones are all the GCCCMS minidisks.
Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total
XMAS91 191 A?? R/W?? 30 3350? 800???????? 18?????? 4051-24????? 13049????? 17100
MNT5E5 5E5 B/B R/O?? 30 3350? 800???????? 11??????? 119-01????? 16981????? 17100
GCC191 120 C?? R/W? 100 3350? 800????????? 7??????? 669-01????? 56331????? 57000
XMAS92 192 D?? R/W?? 30 3350? 800??????? 213?????? 7065-41????? 10035????? 17100
PDPCLB 121 E/C R/O?? 10 3350? 800???????? 17???????? 95-02?????? 5605?????? 5700
GCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700
GCC291 123 G/C R/O? 115 3350? 800???????? 32????? 12303-19????? 53228????? 65531
GCC391 124 H/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC491 125 I/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC591 126 J/C R/O?? 34 3350? 800???????? 84????? 13730-71?????? 5650????? 19380
GCC691 127 K/C R/O?? 45 3350? 800??????? 537????? 19340-75?????? 6310????? 25650
GCC791 128 L/C R/O?? 64 3350? 800??????? 184????? 23041-63????? 13439????? 36480
GCC891 129 M/C R/O?? 40 3350? 800??????? 120?????? 3607-16????? 19193????? 22800
MYTOOL 193 R/R R/O?? 30 3350? 800??????? 185?????? 1217-07????? 15883????? 17100
CMSDSK 190 S?? R/O?? 59 3350? 800??????? 172????? 19533-58????? 14097????? 33630
VMTOOL 196 T/S R/O?? 70 3350? 800???????? 29?????? 1860-05????? 38040????? 39900
MNT19D 19D U/S R/O?? 70 3350? 800??????? 397?????? 5296-13????? 34604????? 39900
MNT19E 19E Y/S R/O?? 70 3350? 800??????? 682????? 24651-62????? 15249????? 39900
Ready; T=0.01/0.01 03:16:01
When I look for all the GCC EXEC files, I get the following. Shouldn't The S-disk version also be on one of the GCCCMS minidisks?
l gcc exec * ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
GCC????? EXEC???? J1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? K1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? Y2? V??? 79??? 272???? 10? 08/03/10?? 19:53
Ready; T=0.01/0.01 03:28:34
Granted my minidisk layout doesn't match, by filemode, the files GCCCMS MEMO.
type gcccms memo c
?
Disk layout for GCCCMS userid February 2021
?
191 A - work disk
291 B - GCC compiler version 3.2.3 MVS 8.5 from 2011
391 C - currently empty
491 D - currently empty
591 E - GCC compiler version 3.2.3 MVS 7.0 from 2009
691 F - GCC & PDPCLIB from 2009? source only
791 G - S, C and H files associated with stuff on F disk?
891 H - GCCLIB version 1.3.1.
?
Ready; T=0.01/0.01 03:33:12
If the 291 minidisk, is the current, production minidisk for VM/370 CE, then should not a copy of GCC EXEC S be on that minidisk as well?
Yours in confusion,
?... Mark S.
|
GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
This might be for Bob Bolch ...
I'm trying to understand too many things, but in any case I end up with the following question. Why does the GCC EXEC S not exist on the GCCCMS minidisks?
When I have the disks accessed as below. The bolded ones are all the GCCCMS minidisks.
Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total
XMAS91 191 A?? R/W?? 30 3350? 800???????? 18?????? 4051-24????? 13049????? 17100
MNT5E5 5E5 B/B R/O?? 30 3350? 800???????? 11??????? 119-01????? 16981????? 17100
GCC191 120 C?? R/W? 100 3350? 800????????? 7??????? 669-01????? 56331????? 57000
XMAS92 192 D?? R/W?? 30 3350? 800??????? 213?????? 7065-41????? 10035????? 17100
PDPCLB 121 E/C R/O?? 10 3350? 800???????? 17???????? 95-02?????? 5605?????? 5700
GCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700
GCC291 123 G/C R/O? 115 3350? 800???????? 32????? 12303-19????? 53228????? 65531
GCC391 124 H/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC491 125 I/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC591 126 J/C R/O?? 34 3350? 800???????? 84????? 13730-71?????? 5650????? 19380
GCC691 127 K/C R/O?? 45 3350? 800??????? 537????? 19340-75?????? 6310????? 25650
GCC791 128 L/C R/O?? 64 3350? 800??????? 184????? 23041-63????? 13439????? 36480
GCC891 129 M/C R/O?? 40 3350? 800??????? 120?????? 3607-16????? 19193????? 22800
MYTOOL 193 R/R R/O?? 30 3350? 800??????? 185?????? 1217-07????? 15883????? 17100
CMSDSK 190 S?? R/O?? 59 3350? 800??????? 172????? 19533-58????? 14097????? 33630
VMTOOL 196 T/S R/O?? 70 3350? 800???????? 29?????? 1860-05????? 38040????? 39900
MNT19D 19D U/S R/O?? 70 3350? 800??????? 397?????? 5296-13????? 34604????? 39900
MNT19E 19E Y/S R/O?? 70 3350? 800??????? 682????? 24651-62????? 15249????? 39900
Ready; T=0.01/0.01 03:16:01
When I look for all the GCC EXEC files, I get the following. Shouldn't The S-disk version also be on one of the GCCCMS minidisks?
l gcc exec * ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
GCC????? EXEC???? J1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? K1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? Y2? V??? 79??? 272???? 10? 08/03/10?? 19:53
Ready; T=0.01/0.01 03:28:34
Granted my minidisk layout doesn't match, by filemode, the files GCCCMS MEMO.
type gcccms memo c
?
Disk layout for GCCCMS userid February 2021
?
191 A - work disk
291 B - GCC compiler version 3.2.3 MVS 8.5 from 2011
391 C - currently empty
491 D - currently empty
591 E - GCC compiler version 3.2.3 MVS 7.0 from 2009
691 F - GCC & PDPCLIB from 2009? source only
791 G - S, C and H files associated with stuff on F disk?
891 H - GCCLIB version 1.3.1.
?
Ready; T=0.01/0.01 03:33:12
If the 291 minidisk, is the current, production minidisk for VM/370 CE, then should not a copy of GCC EXEC S be on that minidisk as well?
Yours in confusion,
?... Mark S.
|
Bill Lewis wrote: [...] You can import the following configuration... [...] You might also try out my Hercules Helper Windows version.
I have added support for VS2022. ... Wow! You appear to be more on top of modern Visual Studio issues than I am, Bill! I still use the older and simpler VS2008 and have only dabbled with VS2017 and VS2019 (and now VS2022). I wasn't aware of all the stuff your Hercules Helper actually does! THANK YOU! Well done! MUCH appreciated! [...] (Also, since this topic really have nothing to do with VM, I suggest
we move the thread to another place.) This being a Hercules BUILD issue and not a VM issue, I would agree. That said, the main Hercules-390 forum might be a better place? Or perhaps opening a new GitHub Issue might be an even better choice? -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
Laddie, You can import the following configuration using Visual Studio Installer, to get the required workloads and individual components required for VS2022. Once Visual Studio Installer is running, click on "More" to get a popup menu and select Import there. Note, if you use this configuration it'll remove any workloads and options you have already installed which aren't in this list.? So perhaps you might use the Export Configuration first, as a backup.
{
? "version": "1.0",
? "components": [
??? "Microsoft.VisualStudio.Component.CoreEditor",
??? "Microsoft.VisualStudio.Workload.CoreEditor",
??? "Microsoft.VisualStudio.Component.Roslyn.Compiler",
??? "Microsoft.Component.MSBuild",
??? "Microsoft.VisualStudio.Component.TextTemplating",
??? "Microsoft.VisualStudio.Component.Debugger.JustInTime",
??? "Microsoft.VisualStudio.Component.VC.CoreIde",
??? "Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
??? "Microsoft.VisualStudio.Component.Windows10SDK.19041",
??? "Microsoft.VisualStudio.Component.VC.Redist.14.Latest",
??? "Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core",
??? "Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions.CMake",
??? "Microsoft.VisualStudio.Component.VC.CMake.Project",
??? "Microsoft.Component.VC.Runtime.UCRTSDK",
??? "Microsoft.VisualStudio.Workload.NativeDesktop",
??? "Microsoft.VisualStudio.Component.Git",
??? "Microsoft.VisualStudio.Component.WinXP"
? ]
}
You might also try out my Hercules Helper Windows version. I have added support for VS2022. While not as complete or robust as it might be, it will handle installing VS for you, including the required workloads and optional components, set up the Property Sheets, clone the SDL repos, grab the zip libs, etc. and do the build, do tests (if you have Rexx installed), and even open firewall rules for Hercules. If you've never heard of the project, you can read about it here: (Also, since this topic really have nothing to do with VM, I suggest we move the thread to another place.) Bill On Sat, Dec 4, 2021 at 05:23 PM, laddiehanus wrote:
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
?
From
The two Property Sheets that we need to modify are the:
Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props
?
without them the build could not find win32.mak
?
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
?
and it works.
?
Its not finding the zipl support files but I am working on it.
?
Laddie Hanus
?
?
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
?
?
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the weekend.
?
Thanks?
?
Laddie Hanus?
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
Read the instructions on Fish¡¯es page?linked below.? Laddie Hanus
On Saturday, December 4, 2021, 5:35 PM, Vince Coen <vbcoen@...> wrote: I'm at a loss now other than XP really you need that O/S ? Best of luck but you could send a msg in the MS community forum area may be some one will know there. Vince On 04/12/2021 23:06, laddiehanus via groups.io wrote: > I installed all the SDK¡¯s including the on for XP > > Laddie > > Sent from whatever device I am using. > >> On Dec 4, 2021, at 4:28 PM, Vince Coen < vbcoen@...> wrote: >> >> ?As a weak guess you might? need to install the Windows SDK that matches 2022. >> >> Vince >> >> >> >>> On 04/12/2021 22:22, laddiehanus via groups.io wrote: >>> I get VS 2022 installed today and I could not find anywhere in the VS directories the following files >>> >>>? From >>> The two Property Sheets that we need to modify are the: >>> >>>? ? /Microsoft.Cpp.Win32.user.props >>>? ? Microsoft.Cpp.x64.user.props / >>> >>> without them the build could not find win32.mak >>> >>> I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0 >>> >>> and it works. >>> >>> Its not finding the zipl support files but I am working on it. >>> >>> Laddie Hanus >>> >>> >>> On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis < wrljet@...> wrote: >>> >>> >>> On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote: >>> >>>? ? I would like the changes but I won¡¯t be able to do much until the >>>? ? weekend. >>>? ? Thanks >>>? ? Laddie Hanus >>> >>> Laddie, >>> >>> Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub. >>> >>> Works on Windows 11 as well. >>> Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail. >>> >>> Bill >>> >>> >>> >>>? ? On Sunday, November 28, 2021, 3:15 PM, Bill Lewis >>>? ? < wrljet@...> wrote: >>> >>>? ? ? ? On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote: >>> >>>? ? ? ? ? ? Been rebuilding my pc after getting rid of windows 11. I >>>? ? ? ? ? ? am doing a clean install. Went to install visual studio >>>? ? ? ? ? ? express and found that the new version is visual studio >>>? ? ? ? ? ? community 2022. I was able to install 2019 earlier this >>>? ? ? ? ? ? month but? the newest older version was 2015 which I don¡¯t >>>? ? ? ? ? ? think has X64 support. >>> >>>? ? ? ? ? ? for the time being I am building on my other computer >>>? ? ? ? ? ? which has 2017 installed >>> >>>? ? ? ? ? ? so has any one tried VS 2022 yet. >>> >>>? ? ? ? ? ? Laddie >>> >>>? ? ? ? Yes, I have tried VS2022.? It works on Windows 10.? On Windows >>>? ? ? ? 11 I'm still working out why some of the tests fail. >>> >>>? ? ? ? But you'll need to modify a couple of the files to build with >>>? ? ? ? it as the repo isn't updated yet. >>>? ? ? ? For a command line build: >>> >>>? ? ? ? ? ? modified: msvc.makefile.includes/VSVERS.msvc >>>? ? ? ? ? ? modified:? vstools.cmd >>> >>>? ? ? ? If you're interested I'll provide the changes. >>> >>>? ? ? ? Bill >>> >> >> >> >> >>
|
I'm at a loss now other than XP really you need that O/S ?
Best of luck but you could send a msg in the MS community forum area may be some one will know there.
Vince
toggle quoted message
Show quoted text
On 04/12/2021 23:06, laddiehanus via groups.io wrote: I installed all the SDK¡¯s including the on for XP
Laddie
Sent from whatever device I am using.
On Dec 4, 2021, at 4:28 PM, Vince Coen <vbcoen@...> wrote:
?As a weak guess you might need to install the Windows SDK that matches 2022.
Vince
On 04/12/2021 22:22, laddiehanus via groups.io wrote:
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From
The two Property Sheets that we need to modify are the:
/Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props /
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the
weekend.
Thanks
Laddie Hanus
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis
<wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I
am doing a clean install. Went to install visual studio
express and found that the new version is visual studio
community 2022. I was able to install 2019 earlier this
month but the newest older version was 2015 which I don¡¯t
think has X64 support.
for the time being I am building on my other computer
which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022. It works on Windows 10. On Windows
11 I'm still working out why some of the tests fail.
But you'll need to modify a couple of the files to build with
it as the repo isn't updated yet.
For a command line build:
modified: msvc.makefile.includes/VSVERS.msvc
modified: vstools.cmd
If you're interested I'll provide the changes.
Bill
|
I installed all the SDK¡¯s including the on for XP
Laddie
Sent from whatever device I am using.
toggle quoted message
Show quoted text
On Dec 4, 2021, at 4:28 PM, Vince Coen <vbcoen@...> wrote:
?As a weak guess you might need to install the Windows SDK that matches 2022.
Vince
On 04/12/2021 22:22, laddiehanus via groups.io wrote:
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From
The two Property Sheets that we need to modify are the:
/Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props /
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the
weekend.
Thanks
Laddie Hanus
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis
<wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I
am doing a clean install. Went to install visual studio
express and found that the new version is visual studio
community 2022. I was able to install 2019 earlier this
month but the newest older version was 2015 which I don¡¯t
think has X64 support.
for the time being I am building on my other computer
which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022. It works on Windows 10. On Windows
11 I'm still working out why some of the tests fail.
But you'll need to modify a couple of the files to build with
it as the repo isn't updated yet.
For a command line build:
modified: msvc.makefile.includes/VSVERS.msvc
modified: vstools.cmd
If you're interested I'll provide the changes.
Bill
|
As a weak guess you might? need to install the Windows SDK that matches 2022.
Vince
toggle quoted message
Show quoted text
On 04/12/2021 22:22, laddiehanus via groups.io wrote: I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From
The two Property Sheets that we need to modify are the:
/Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props /
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the
weekend.
Thanks
Laddie Hanus
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis
<wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I
am doing a clean install. Went to install visual studio
express and found that the new version is visual studio
community 2022. I was able to install 2019 earlier this
month but ?the newest older version was 2015 which I don¡¯t
think has X64 support.
for the time being I am building on my other computer
which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows
11 I'm still working out why some of the tests fail.
But you'll need to modify a couple of the files to build with
it as the repo isn't updated yet.
For a command line build:
??? modified: msvc.makefile.includes/VSVERS.msvc
??? modified:?? vstools.cmd
If you're interested I'll provide the changes.
Bill
|
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From The two Property Sheets that we need to modify are the:
Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the weekend.
?
Thanks?
?
Laddie Hanus?
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the weekend.
?
Thanks?
?
Laddie Hanus?
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
I would like the changes but I won¡¯t be able to do much until the weekend.
Thanks?
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote: On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
|
Marco Antoniotti
Mark A. Stevens
Bill Lewis