I suggest you learn a build system, whether it be classic makefiles,
msbuild or something else. MSBuild in particular allows you to set
command line options as xml elements, you don't need to know what the
property gets translated to. Writing cl.exe command lines is the very
hard way to go about it.
On 10/29/18, BobJ <rjustice004@xxxxxxxxxx> wrote:
Hello, Dante,
Thanks for your response.
I discovered, while experimenting, that I was using the wrong command-line
switch so, this code compiles when I use the /o switch instead.
The next thing I need to discover is why, when I use the /o switch, the
compiler issues a warning stating that the /o switch has been deprecated and
will be REMed out in a later version. However, when I type cl /?, the output
lists several /o* combinations and, although I haven't tried all of those,
the ones I have tried result in errors and fail.
Thanks for any assistance.
Bob, still experimenting.
From: Dante Gagne (Redacted sender "danteg" for DMARC)
Sent: Monday, October 29, 2018 1:31 PM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: C/C++ command-line compiler - was VS2017: Two
issues
Hey Bob,
Sorry, but I’m not a C/C++ guy… honestly, I haven’t done those languages in
a long time. I’ll see if I can find a contact on the C++ team who might
know, but you might try StackOverflow to see if someone there can help.
--Dante
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On
Behalf Of BobJ
Sent: Saturday, October 27, 2018 10:01 AM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: C/C++ command-line compiler - was VS2017: Two
issues
Can anybody explain what is going awry here?
------------------ begin screen shot -----------------
Developer Command Prompt for VS 2017
c:\hello>cl /EHsc HelloC hello.c
Microsoft (R) C/C++ Optimizing Compiler Version 19.15.26732.1 for x86
Copyright (C) Microsoft Corporation. All rights reserved.
cl : Command line warning D9024 : unrecognized source file type 'HelloC',
object
file assumed
hello.c
Microsoft (R) Incremental Linker Version 14.15.26732.1
Copyright (C) Microsoft Corporation. All rights reserved.
/out:HelloC.exe
HelloC
hello.obj
LINK : fatal error LNK1181: cannot open input file 'HelloC.obj'
c:\hello>
------------------ end screen shot -----------------
-------------------------- begin hello.c file ----------------------------
#include <stdio.h>
void main()
{
printf("Hello, world, from Visual C! /n");
}
-------------------------- end hello.c file ----------------------------
System Information
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor AMD FX(tm)-4130 Quad-Core Processor, 3800 Mhz, 2 Core(s), 4
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 4.00 GB
Available Physical Memory 1.68 GB
Total Virtual Memory 8.00 GB
Any help appreciated!
Bob
From: BobJ
Sent: Monday, October 22, 2018 11:09 AM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] C/C++ command-line compiler - was VS2017: Two issues
30 years ago, I did some C and C++ programming and, aside from the need to
creat a make file and using a linker, it was fairly simple to creat a *.exe
file.
Today, I have yet to find a compiler that can manage to compile the
following code:
------------------ begin snipit ---------------------------
#include <stdio.h>
int main()
{
printf("Hello, World! \n");
return 0;
}
------------------------ end snipit -----------------------------------
There may be some errors in that code even though I have tried several
variations for the pre-processor line.
When I have had any response from one of the compilers I have tried, GCC,
there are many lines of warning messages stating the null characters have
been ignored. I can't find any null characterrs in that code.
My OS is Win7, 64-bit and I use NVDA and/or JFW, as appropriate.
Any suggestions?
TIA,
Bob
From: Jordy Deweer
Sent: Sunday, October 21, 2018 4:25 AM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: VS2017: Two issues
Soronel Haetir wrote:
The notification crash is a known issue and so far as I know we're still
waiting on a fix.
Are there ways to avoid crashing? And how long has it been going on?
On 10/20/2018 10:39 PM, Soronel Haetir wrote:
The notification crash is a known issue and so far as I know we'restill
waiting on a fix. On 10/20/18, Jordy Deweer <jordyydeweer@xxxxxxxxx>
wrote:Dear all I have two issues with Visual Studio 2017 (Community). The
first problem is the following: when I work with the Team Explorer(to
manipulate Git), everything works fine, until I commited something.After
commiting, an extra part in the window appears, which ontainsnotifications.
If I press Tab to go back to the list of, for example,unstaged items, I need
to pass-by that notifications area. But, VScrashes as soon as the
notifications area gets the focus (using tab). Isthat a known problem, can
it be resolved by a modification in thesettings, etc.? When tere are errors
and I try to read the notificationsfrom the Team Explorer window, the first
line goes well, but as soon asI press one of the panning buttons on my Focus
40 Blue (4th Gen) brailledisplay, everything crashes as well, just like it
does when tere are noerrors and the notifications box get the focus... My
second problem is that, when I am using JAWS 2018 to edit code, ithappens
that the braille stays on the "mnu text editor" message ofIntelliSense,
while I am back in the code itself with my focus. Thespeech works fine
though. I tried maximalizing the window, restartingeverything, but it did
not resolve the problem. Hereby needs to be saidthat it doesn't always
happen. When I am in trouble, a simpel restart ofJAWS is enough to solve
everything- until it happens again. Is there a way to solve the above
problems or will there need to be bugfixes in Visual Studio? Thanks in
advance for possible replies. Yours faithfully Jordy Deweer ** To leave the
list, click on the immediately-following link:-**
[mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]** If this link
doesn't work then send a message to:** program-l-request@xxxxxxxxxxxxx** and
in the Subject line type** unsubscribe** For other list commands such as
vacation mode, click on the** immediately-following link:-**
[mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]** or send a message,
to** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
