Problems with cygwin build dll for use in windows app
I use Cygwin to build source code to DLL used by windows app.
When I use GCC core / GCC g++, the app crash if it calls function (which includes printf or malloc) in DLL.
When I use Mingw64-x86_64-gcc-core / Mingw64-x86_64-gcc-g++ it reports error like sys/socket.h：No such file or directory.
Can anyone explain how to do it? Thanks.
dll cygwin
edited Nov 16 '18 at 6:05
kit
1,10631017
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
add a comment |
I use Cygwin to build source code to DLL used by windows app.
When I use GCC core / GCC g++, the app crash if it calls function (which includes printf or malloc) in DLL.
When I use Mingw64-x86_64-gcc-core / Mingw64-x86_64-gcc-g++ it reports error like sys/socket.h：No such file or directory.
Can anyone explain how to do it? Thanks.
dll cygwin
edited Nov 16 '18 at 6:05
kit
1,10631017
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
add a comment |
I use Cygwin to build source code to DLL used by windows app.
When I use GCC core / GCC g++, the app crash if it calls function (which includes printf or malloc) in DLL.
When I use Mingw64-x86_64-gcc-core / Mingw64-x86_64-gcc-g++ it reports error like sys/socket.h：No such file or directory.
Can anyone explain how to do it? Thanks.
dll cygwin
edited Nov 16 '18 at 6:05
kit
1,10631017
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
I use Cygwin to build source code to DLL used by windows app.
When I use GCC core / GCC g++, the app crash if it calls function (which includes printf or malloc) in DLL.
When I use Mingw64-x86_64-gcc-core / Mingw64-x86_64-gcc-g++ it reports error like sys/socket.h：No such file or directory.
Can anyone explain how to do it? Thanks.
dll cygwin
dll cygwin
edited Nov 16 '18 at 6:05
kit
1,10631017
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
edited Nov 16 '18 at 6:05
kit
1,10631017
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
edited Nov 16 '18 at 6:05
kit
1,10631017
edited Nov 16 '18 at 6:05
kit
1,10631017
edited Nov 16 '18 at 6:05
kit
1,10631017
1,10631017
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
asked Nov 16 '18 at 5:00
Wang HaiWang Hai
58116
58116
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The first problem is due to the tentative to build a stand alone DLL (not depending on cygwin1.dll) using cygwin only specific tools.
You have collision between multiple malloc and other C library call present in cygwin1.dll.
The second is due to the fact that sys/socket.h does not exist on Windows
see for possible solution:
Using sys/socket.h functions on windows
So you need to define what is your target : Cygwin/Posix or Windows and choose programming style and tools accordingly, you can not mix.
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
Hi, for the first problem, I build a DLL (depends on cygwin1.dll), and create a windows console app with Visual Studio to load the DLL, and call a function in it. If the function contains malloc, the app crashes. So Why there are multiple malloc? Thanks.
– Wang Hai
Nov 17 '18 at 6:08
Visual Studio program uses the Windows C malloc, the Cygwin DLL uses the one in cygwin1.dll. You need to use the same tools for both app and dll
– matzeri
Nov 17 '18 at 6:53
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53331713%2fproblems-with-cygwin-build-dll-for-use-in-windows-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The first problem is due to the tentative to build a stand alone DLL (not depending on cygwin1.dll) using cygwin only specific tools.
You have collision between multiple malloc and other C library call present in cygwin1.dll.
The second is due to the fact that sys/socket.h does not exist on Windows
see for possible solution:
Using sys/socket.h functions on windows
So you need to define what is your target : Cygwin/Posix or Windows and choose programming style and tools accordingly, you can not mix.
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
Hi, for the first problem, I build a DLL (depends on cygwin1.dll), and create a windows console app with Visual Studio to load the DLL, and call a function in it. If the function contains malloc, the app crashes. So Why there are multiple malloc? Thanks.
– Wang Hai
Nov 17 '18 at 6:08
Visual Studio program uses the Windows C malloc, the Cygwin DLL uses the one in cygwin1.dll. You need to use the same tools for both app and dll
– matzeri
Nov 17 '18 at 6:53
add a comment |
The first problem is due to the tentative to build a stand alone DLL (not depending on cygwin1.dll) using cygwin only specific tools.
You have collision between multiple malloc and other C library call present in cygwin1.dll.
The second is due to the fact that sys/socket.h does not exist on Windows
see for possible solution:
Using sys/socket.h functions on windows
So you need to define what is your target : Cygwin/Posix or Windows and choose programming style and tools accordingly, you can not mix.
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
Hi, for the first problem, I build a DLL (depends on cygwin1.dll), and create a windows console app with Visual Studio to load the DLL, and call a function in it. If the function contains malloc, the app crashes. So Why there are multiple malloc? Thanks.
– Wang Hai
Nov 17 '18 at 6:08
Visual Studio program uses the Windows C malloc, the Cygwin DLL uses the one in cygwin1.dll. You need to use the same tools for both app and dll
– matzeri
Nov 17 '18 at 6:53
add a comment |
The first problem is due to the tentative to build a stand alone DLL (not depending on cygwin1.dll) using cygwin only specific tools.
You have collision between multiple malloc and other C library call present in cygwin1.dll.
The second is due to the fact that sys/socket.h does not exist on Windows
see for possible solution:
Using sys/socket.h functions on windows
So you need to define what is your target : Cygwin/Posix or Windows and choose programming style and tools accordingly, you can not mix.
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
The first problem is due to the tentative to build a stand alone DLL (not depending on cygwin1.dll) using cygwin only specific tools.
You have collision between multiple malloc and other C library call present in cygwin1.dll.
The second is due to the fact that sys/socket.h does not exist on Windows
see for possible solution:
Using sys/socket.h functions on windows
So you need to define what is your target : Cygwin/Posix or Windows and choose programming style and tools accordingly, you can not mix.
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
answered Nov 16 '18 at 17:10
matzerimatzeri
4,152268
4,152268
Hi, for the first problem, I build a DLL (depends on cygwin1.dll), and create a windows console app with Visual Studio to load the DLL, and call a function in it. If the function contains malloc, the app crashes. So Why there are multiple malloc? Thanks.
– Wang Hai
Nov 17 '18 at 6:08
Visual Studio program uses the Windows C malloc, the Cygwin DLL uses the one in cygwin1.dll. You need to use the same tools for both app and dll
– matzeri
Nov 17 '18 at 6:53
add a comment |
Hi, for the first problem, I build a DLL (depends on cygwin1.dll), and create a windows console app with Visual Studio to load the DLL, and call a function in it. If the function contains malloc, the app crashes. So Why there are multiple malloc? Thanks.
– Wang Hai
Nov 17 '18 at 6:08
Visual Studio program uses the Windows C malloc, the Cygwin DLL uses the one in cygwin1.dll. You need to use the same tools for both app and dll
– matzeri
Nov 17 '18 at 6:53
Hi, for the first problem, I build a DLL (depends on cygwin1.dll), and create a windows console app with Visual Studio to load the DLL, and call a function in it. If the function contains malloc, the app crashes. So Why there are multiple malloc? Thanks.
– Wang Hai
Nov 17 '18 at 6:08
Hi, for the first problem, I build a DLL (depends on cygwin1.dll), and create a windows console app with Visual Studio to load the DLL, and call a function in it. If the function contains malloc, the app crashes. So Why there are multiple malloc? Thanks.
– Wang Hai
Nov 17 '18 at 6:08
Visual Studio program uses the Windows C malloc, the Cygwin DLL uses the one in cygwin1.dll. You need to use the same tools for both app and dll
– matzeri
Nov 17 '18 at 6:53
Visual Studio program uses the Windows C malloc, the Cygwin DLL uses the one in cygwin1.dll. You need to use the same tools for both app and dll
– matzeri
Nov 17 '18 at 6:53
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53331713%2fproblems-with-cygwin-build-dll-for-use-in-windows-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
