NO

Recent Posts

Pages: 1 ... 8 9 [10]
91
Add-ins / Re: CppFile Add-In, a modified version
« Last post by bitcoin on August 21, 2019, 12:00:52 am »
Ok, but I again have error "fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory"

I put in Ini file path for my studio..
[include]
include0=/I"c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\include"
include1=/I"c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include"
include2=/I"C:\Program Files\Microsoft Visual Studio\MFC\Include"
92
Add-ins / Re: CppFile Add-In, a modified version
« Last post by TimoVJL on August 20, 2019, 11:55:19 pm »
Unselect cppfile and select that CppFile 2.1 and try again, but poide need to restart.
93
Add-ins / Re: CppFile Add-In, a modified version
« Last post by bitcoin on August 20, 2019, 11:21:40 pm »
Thank you, but this button is inactive


And I have error 'fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory'

But I added folders from Visual Studio (lib, bin, inc) and even DDK. No result.
94
Add-ins / AddInLoad, Add-In loader
« Last post by TimoVJL on August 19, 2019, 08:59:41 pm »
Pelles C poide users can create their own Add-In loaders, an example provided.
Before starting poide, download Add-Ins to avoid file locking errors.
Put AddInLoad to Pelles C bin folder and start it from there, as admin, if necessary.
An example offers to download some of Add-Ins from my limited collection.
UI is quite simple. It create AddIns/AddIns64 folder, if needed, like in temporary folder for testing.

Generate Files.lst
Code: [Select]
#define WIN32_LEAN_AND_MEAN
#include <stdio.h>
#include <windows.h>

#pragma comment(lib,"version.lib")
#pragma comment(lib,"user32.lib")
#pragma comment(lib,"msvcrt.lib")

void __cdecl mainCRTStartup(void)
{
int __cdecl main(int argc, char **argv);
int __cdecl __getmainargs(int*, char***, char***, int, void*);
void __cdecl exit(int status);

int    argc;
char** argv;
char** env;
int    sinfo = 0;

__getmainargs(&argc,&argv,&env,0,&sinfo);
exit(main(argc,argv));
}

LPSTR GetVersionInfo(TCHAR *szFileName, TCHAR *szValue, TCHAR *szBuffer, ULONG nLength)
{
LPSTR csRet;
DWORD len;

csRet = NULL;
len = GetFileVersionInfoSize(szFileName, 0);
if (len) {
csRet = NULL;
LPVOID ver = LocalAlloc(LPTR, len);
if (ver != NULL)
{
DWORD *codepage;
char fmt[256];
PVOID ptr = 0;
if (GetFileVersionInfo(szFileName, 0, len, ver))
{
if (VerQueryValue(ver, "\\VarFileInfo\\Translation", (LPVOID) & codepage, &len))
{
wsprintf(fmt, "\\StringFileInfo\\%08x\\%s", (*codepage) << 16 | (*codepage) >> 16, szValue);
if (VerQueryValue(ver, fmt, &ptr, &len))
{
lstrcpyn(szBuffer, (TCHAR *)ptr, min(nLength, len));
csRet = szBuffer;
}
}
}
LocalFree(ver);
}
}
return csRet;
}

int DoWithMask(char *szMask) {
WIN32_FIND_DATA fdFile;
HANDLE hFile;
int iPos, iIdx = 1;
char szTmp[MAX_PATH];

iPos = lstrlen(szMask) - 5;
lstrcpyn(szTmp, szMask, iPos);
iPos--;
hFile = FindFirstFile(szMask, &fdFile);
if (hFile != INVALID_HANDLE_VALUE)
do {
if ((fdFile.dwFileAttributes & FILE_ATTRIBUTE_DIRECTORY)
!= FILE_ATTRIBUTE_DIRECTORY) {
char szVer[100];
WIN32_FILE_ATTRIBUTE_DATA fad;
*szVer = 0;
printf(fdFile.cFileName);
*(szTmp+iPos) = '\\'; // put back
lstrcpy(szTmp+iPos+1, fdFile.cFileName);
GetFileAttributesEx(szTmp, GetFileExInfoStandard,&fad);
if (GetVersionInfo(szTmp, "ProductVersion", szVer, sizeof(szVer)))
printf("\t%s", szVer);
else
printf("\t");
SYSTEMTIME st;
FileTimeToSystemTime(&fad.ftLastWriteTime, &st);
printf("\t%u-%02u-%02u", st.wYear, st.wMonth, st.wDay);
printf("\t%u", fad.nFileSizeLow);
if (GetVersionInfo(szTmp, "FileDescription", szVer, sizeof(szVer)))
printf("\t%s", szVer);
else
printf("\t");
printf("\t%llu\n", fad.ftLastWriteTime); // timestamp
iIdx++;
}
} while (FindNextFile(hFile, &fdFile));
FindClose(hFile);
return 0;
}

int main(int argc, char **argv)
{
DoWithMask(argv[1]);
return 0;
}
95
Expert questions / Re: system cannot find the file specified
« Last post by tony74 on August 19, 2019, 03:57:48 pm »
Thanks, Timo. Yes it was an Avira issue.

polink.exe was missing from the \bin dir.
Thanks to your hint, I checked Avira's Quarantine list, found polink listed and restored it.

I tried a compile, Avira flagged polink again, I set it to 'Allow' and ran several more compiles.

All seems to be working normally, must have been an Avira update that included new virus footprints that triggered the quarantine.

Thanks again, Timo.
96
Expert questions / Re: system cannot find the file specified
« Last post by TimoVJL on August 19, 2019, 11:38:36 am »
Can you execute polink.exe, is it a virus scanner issue ?
97
Expert questions / system cannot find the file specified
« Last post by tony74 on August 19, 2019, 04:34:17 am »
Code: [Select]
Building C:\aCode\roll\output\roll.obj.
Building C:\aCode\roll\roll.exe.
*** Error: polink.exe -subsystem:console -machine:x86 -safeseh kernel32.lib advapi32.lib delayimp.lib -out:"C:\aCode\roll\roll.exe" C:\aCode\roll\output\roll.obj
*** Error: The system cannot find the file specified. 
Done.

Running 9.00.9, been using it with no issues since it's release.

Regardless of the code or it's directory, I get this error. It builds the .obj, but polink fails to find it (I guess).

Nothings changed in the Pellesc install dirs, I have no idea unless a system PATH setup has changed, but if Pelles made the directories and the compile script, wouldn't polink know where to find the obj regardless of PATH (unless it's polink.exe that can't be found...)?
98
Chit-Chat / Re: List of C compiler for Windows
« Last post by Abraham on August 19, 2019, 04:11:26 am »
TCC and PCC are limited to C99.

Not sure about Visual C++ and it's weird reverse compatibility.
C11 took atomic and thread from C++11, so it has those as well.
C++11 requires most of C99, except for a few things like VLA.
C++14 requires many things from C11, but not everything.
There is not need to support _Generic because templates are better in C++.

MinGW and Clang are up to standards.

POCC is clearly the one in the lead to matching standards.
99
Add-ins / PrjPO10DbgLines64.dll
« Last post by TimoVJL on August 17, 2019, 03:28:03 pm »
An Add-In for PellesC 9 debug format.
Just show lines for usable breakpoints.
100
Bug reports / Re: Debugger in Pelles C IDE 9.00.9 is wrong
« Last post by frankie on August 14, 2019, 04:56:33 pm »
It's a debug info problem in v9, not quite a debugger problem.
Well, the point seems to be that the debug info specify a line number that points to a compare/jump instruction sequence that aren't the correct location for the breakpoint.
What is missing is a smart routine that interpret the sequence and moves breakpoint to the correct execution point, that is the jumped location.
Easy to say a little bit more difficult to code...  :(
Pages: 1 ... 8 9 [10]