Recent Posts

71

Feature requests / Re: Option for "Executable" path per project

« Last post by TimoVJL on March 14, 2022, 03:15:40 pm »

Meanwhile.
poide have -xml option, so different .xml files for poide, for simulating "Executable" paths.

72

Feature requests / Re: Option for "Executable" path per project

« Last post by rapte on March 14, 2022, 02:16:31 am »

Thank you Pelle

73

User contributions / Re: wininet sample

« Last post by frankie on March 14, 2022, 12:39:48 am »

 

74

User contributions / Re: wininet sample

« Last post by CLR on March 13, 2022, 11:59:58 pm »

The sample has been updated, now using another API. 

75

Feature requests / Re: Option for "Executable" path per project

« Last post by Pelle on March 13, 2022, 09:02:11 pm »

I haven't touched this part of the code for a long time, so it's not at the top of my head. A quick search suggests it would affect multiple places (always less pleasing than a single place to change). I will look at it some more later... For now it's a "maybe"...

76

Feature requests / Re: Option for "Executable" path per project

« Last post by rapte on March 12, 2022, 07:33:13 pm »

Hi TimoVJL,

Project options: Working directory: is the correct place where the dlls should go. However what I meant was that it would be nice if the third party library BIN folder (where the dlls are placed) could be added in the path per project just as INCLUDE and LIB. The dlls could be copied from their original location only when the project was ready to be shared.

A hypothetical case: There are 10 projects of SDL2 32-bit and 64-bit each of them requiring their five dlls each for 32-bit and 64-bit in their working directory. A new version of SDL2, SDL_image and SDL_ttf is updated by replacing the old SDL folder with the new SDL folder. The project INCLUDE and LIB variables will magically point to the updated libraries, howerver all the dlls in the working directory will have to be replaced manually.

As I have mentioned earlier, this can be done in Tools -> Options -> Projects -> Folders -> Type (Executables | Libraries | Includes), but it is done globally not per project.

Thanks

77

Feature requests / Re: Option for "Executable" path per project

« Last post by TimoVJL on March 11, 2022, 12:53:12 pm »

Project options: Working directory: wasn't, what you was after ?
 

78

Feature requests / Option for "Executable" path per project

« Last post by rapte on March 09, 2022, 02:21:49 pm »

It would be really nice if the "Executables" option was added for Projects where the path for the dlls could be updated (Project -> Project Options -> Folders -> Type (Libraries | Includes | Executables). Currently we have to copy the dlls to the folder of the exe. It is useful if a number of projects require the same dlls.

I know that this can also be done with Tools -> Options -> Projects -> Folders -> Type (Executables | Libraries | Includes), but it is done globally for all the projects.

I am using Pelles C version 11.00.2

thanks

79

User contributions / Re: SGL - win32 made simple!

« Last post by 1e9t8m29 on March 01, 2022, 01:13:22 pm »

Hi. Is this library still in development? I go to this forum from the FreeBASIC binding of this library here:

https://github.com/ruanjiaxing/SGL-FreeBASIC

The developer's account now is a guest so it seems he's not there for a long time.

80

Tips & tricks / Calling API functions in inline assembly code

« Last post by Vortex on February 27, 2022, 02:02:00 pm »

Hello,

Here is a quick example :

Code: [Select]

// Source code built with PellesC 11.00.2

#include <stdio.h>
#include <windows.h>
char t1[]="This is a test1.";
char t2[]="This is a test2.";

int APIENTRY wWinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, WCHAR *pszCmdLine, int nCmdShow)
{
__asm{

push 0
push OFFSET t1
push OFFSET t1
        push 0
call DWORD PTR [MessageBox]
}

MessageBox(0,t2,t2,0);
return 0;
}

The API function MessageBox in the inline asm block should be enclosed between square brackets otherwise wrong call to API will lead to application crash.