Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(371) |
Oct
(167) |
Nov
(412) |
Dec
(208) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(378) |
Feb
(302) |
Mar
(269) |
Apr
(296) |
May
(306) |
Jun
(381) |
Jul
(346) |
Aug
(315) |
Sep
(195) |
Oct
(216) |
Nov
(280) |
Dec
(227) |
2002 |
Jan
(309) |
Feb
(333) |
Mar
(328) |
Apr
(407) |
May
(517) |
Jun
(519) |
Jul
(400) |
Aug
(580) |
Sep
(1273) |
Oct
(984) |
Nov
(683) |
Dec
(538) |
2003 |
Jan
(578) |
Feb
(454) |
Mar
(312) |
Apr
(366) |
May
(505) |
Jun
(431) |
Jul
(415) |
Aug
(374) |
Sep
(470) |
Oct
(578) |
Nov
(372) |
Dec
(309) |
2004 |
Jan
(308) |
Feb
(247) |
Mar
(372) |
Apr
(413) |
May
(333) |
Jun
(323) |
Jul
(269) |
Aug
(239) |
Sep
(469) |
Oct
(383) |
Nov
(400) |
Dec
(332) |
2005 |
Jan
(411) |
Feb
(363) |
Mar
(346) |
Apr
(316) |
May
(275) |
Jun
(248) |
Jul
(396) |
Aug
(396) |
Sep
(279) |
Oct
(340) |
Nov
(319) |
Dec
(218) |
2006 |
Jan
(317) |
Feb
(263) |
Mar
(304) |
Apr
(296) |
May
(209) |
Jun
(349) |
Jul
(246) |
Aug
(198) |
Sep
(174) |
Oct
(138) |
Nov
(201) |
Dec
(270) |
2007 |
Jan
(223) |
Feb
(182) |
Mar
(350) |
Apr
(350) |
May
(259) |
Jun
(221) |
Jul
(299) |
Aug
(465) |
Sep
(356) |
Oct
(265) |
Nov
(417) |
Dec
(225) |
2008 |
Jan
(421) |
Feb
(327) |
Mar
(219) |
Apr
(389) |
May
(375) |
Jun
(262) |
Jul
(215) |
Aug
(289) |
Sep
(257) |
Oct
(383) |
Nov
(237) |
Dec
(209) |
2009 |
Jan
(232) |
Feb
(327) |
Mar
(306) |
Apr
(251) |
May
(146) |
Jun
(247) |
Jul
(302) |
Aug
(252) |
Sep
(263) |
Oct
(376) |
Nov
(270) |
Dec
(244) |
2010 |
Jan
(225) |
Feb
(184) |
Mar
(300) |
Apr
(290) |
May
(275) |
Jun
(535) |
Jul
(192) |
Aug
(237) |
Sep
(304) |
Oct
(142) |
Nov
(384) |
Dec
(186) |
2011 |
Jan
(305) |
Feb
(337) |
Mar
(331) |
Apr
(318) |
May
(306) |
Jun
(299) |
Jul
(205) |
Aug
(271) |
Sep
(232) |
Oct
(179) |
Nov
(252) |
Dec
(216) |
2012 |
Jan
(195) |
Feb
(268) |
Mar
(142) |
Apr
(226) |
May
(203) |
Jun
(132) |
Jul
(211) |
Aug
(429) |
Sep
(289) |
Oct
(291) |
Nov
(182) |
Dec
(188) |
2013 |
Jan
(205) |
Feb
(259) |
Mar
(224) |
Apr
(125) |
May
(295) |
Jun
(181) |
Jul
(209) |
Aug
(167) |
Sep
(330) |
Oct
(212) |
Nov
(95) |
Dec
(114) |
2014 |
Jan
(40) |
Feb
(63) |
Mar
(62) |
Apr
(65) |
May
(82) |
Jun
(105) |
Jul
(56) |
Aug
(175) |
Sep
(79) |
Oct
(49) |
Nov
(51) |
Dec
(47) |
2015 |
Jan
(26) |
Feb
(69) |
Mar
(82) |
Apr
(55) |
May
(35) |
Jun
(57) |
Jul
(54) |
Aug
(56) |
Sep
(25) |
Oct
(21) |
Nov
(8) |
Dec
(27) |
2016 |
Jan
(49) |
Feb
(44) |
Mar
(132) |
Apr
(39) |
May
(39) |
Jun
(49) |
Jul
(70) |
Aug
(43) |
Sep
(69) |
Oct
(79) |
Nov
(65) |
Dec
(32) |
2017 |
Jan
(99) |
Feb
(88) |
Mar
(42) |
Apr
(47) |
May
(56) |
Jun
|
Jul
(79) |
Aug
(9) |
Sep
(29) |
Oct
(4) |
Nov
|
Dec
(12) |
2018 |
Jan
(45) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
1
(10) |
2
(10) |
3
(5) |
4
(7) |
5
(8) |
6
(11) |
7
(16) |
8
(7) |
9
(2) |
10
(16) |
11
(11) |
12
(9) |
13
(12) |
14
(9) |
15
(5) |
16
(4) |
17
(12) |
18
(17) |
19
(13) |
20
(5) |
21
(13) |
22
(19) |
23
(12) |
24
(22) |
25
(9) |
26
(6) |
27
(7) |
28
(7) |
29
(27) |
30
(22) |
31
(13) |
|
|
From: Michael Gerdau <mgd@te...> - 2005-03-23 18:47:13
|
> The problem is: Some of the dll files are already created in UNIX system > (take any UNIX system). I need to convert them to Windows compatible dll > files so that I can load those dll files and call the functions from MS > VC++.=20 > Can any one please help in this regard with stepwise explanation? You need to provide some more information here. 1) Are you talking about binaries that are used on a UNIX system (take any UNIX system) that you want to convert somehow to be used on a Windows system ? 2) Are you talking about some code that you have in source (on a UNIX system (take any UNIX system)) and that you now wish to convert into a Windows compatible DLL ? If 1) then others already wrote this is most certainly impossible for all practical cases, i.e. the answer to your question is: This can't be done. If 2) then you either have to use a UNIX-hosted crosscompiler to create Windows compatible DLLs (as others already suggested) and probably nothing else is required -- or you have to take the source and port the stuff to Windows. You wish to do a new port of UNIX sources to a Windows DLL then for creating the DLL there is an explanation in the MinGWiki whose URL has already been posted in this thread. Rest assured that creating the DLL probably will be the least of your problems though... Anyway: If you wish to get more detailed advice you'll have to ask a more detailed question. HTH, best, Michael =2D-=20 Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mgd@... GPG-keys available on request or at public keyserver |
From: SourceForge.net <noreply@so...> - 2005-03-23 17:52:37
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3063617 By: py9bpl Thanks for the replies. This seems to be a bit of a difficult issue. I've finished the simple MinGW port I discussed in my original post. I'll knock up a couple of Dev-C++ project files as well as the makefiles I've got so people can use Dev-C++ as well. My plan is to then upload what I've called the "Quake2MinGWBaseCode" to the SourceForge project as a file release. Here's a couple of snips from the long readme file I was going to include (it took me hours to write and it's still probably wrong): ... [Note that the following arguments in this section represent my view of the situation. Please see the discussion "Possible License Violations" below for other important points] For compiled binaries to comply with the GPL, Quake 2's use of Microsoft's DirectX library had to be removed. This is because although MinGW comes with GPL compatible versions of the Win32 API, it doesn't come with any version of the DirectX SDK. If DirectX were to be used, the DirectX source code would have to accompany any binaries compiled from this distribution (this is a requirement of the GPL), but the DirectX license does not allow this. ... ... Possible License Violations --------------------------- In my mind there are two problems with distributing Visual C++ compiled binaries built from the original 3.21 source: the Microsoft supplied C-Runtime/Win32 API libraries and DirectX. Quake 2 makes extensive use of the C Runtime Library (CRT) and the Win32 API. Although most linking will be performed at runtime, it is my belief that enough code from these libraries will be included with the executable and dlls that distribution of such files must comply with the license terms for redistributing these components. The Microsoft End-User License Agreement quite clearly prohibits GPL compatible distribution of such binaries. In my opinion, terms of the license agreement for DirectX quite clearly prohibit GPL distribution of the DirectX headers and libraries. However, there is an argument that DirectX source code need not accompany any compiled binaries because DirectX comes pre-installed on modern Windows operating systems (this is a special exception in the GPL). Even though Quake 2 makes use of DirectX by using LoadLibrary() rather than linking directly with DirectX libraries, it must still use Microsoft supplied headers. This means that some amount of code from the DirectX SDK will end up in the binary, even if it is a very small amount. Whether such use of header files is deemed as 'fair use' is not well defined by law (this point is mentioned in the GPL). If it is not 'fair use' then the GPL is violated because parts of DirectX would be deemed to accompany the executable, which would thus require inclusion of DirectX source code with the distribution. The DirectX license would also be violated because it then prohibits GPL distribution of compiled binaries. It is quite possible that Quake 2's use of DirectX *might* constitute 'fair use', but I am not a lawyer so it is simply safer for me to not use DirectX. Note that directly linking to DirectX libraries or more extensive use of DirectX features such as D3DX is less likely to be allowed. Even if it is allowed, DirectX is not free software so use of a different library that is free software would be preferred for GPL distribution of Quake 2. ... What do you think? ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=7134 |
From: Keith MARSHALL <keith.marshall@to...> - 2005-03-23 16:32:29
|
>> The trailing @number is not C++ decoration. It is actually >> one of the things that __stdcall is for. The number is the >> number of bytes passed to the routine so that the called >> routine can clean the stack rather than the caller. > > Why would you want to do that? If you need to ask, you probably don't want to know! It's dependent on the function calling protocol used by the compiler. When the language is C or C++, the calling routine pushes arguments from right to left on to the stack, calls the function, saves the return value, and removes the arguments from the stack. This protocol is required, to support functions which can have varying numbers of arguments, and absolves the called routine from needing any knowledge of the number of actual arguments passed, (provided sufficient are provided, to satisfy its needs). When the language is Pascal, or FORTRAN, the calling routine pushes arguments from left to right, and calls the function, subroutine(FORTRAN) or procedure(Pascal); it expects the called routine to remove its arguments from the stack, *before* it returns. This protocol is suitable only for functions, subroutines and procedures which accept a fixed number and type of arguments, which, of course, is a limitation imposed on FORTRAN and Pascal functions, subroutines and procedures. In the MS-DOS days, Microsoft were heavily committed to the use of Pascal in their OS development, and this continued into Windows development; most of the Windows API's use the Pascal argument passing protocol. Regards, Keith. |
From: Tor Lillqvist <tml@ik...> - 2005-03-23 16:14:03
|
Anirban Mazumder writes: > Can any one please help in this regard with stepwise explanation? No, because what you ask for doesn't make sense. You must explain in more detail what it is you actually want to do. Unix systems don't use files that would be called "DLLs". Are you talking about DLLs that really *are* Windows DLLs, i.e. produced by a cross-compiler running on Unix? Or are you talking about Unix shared libraries? (On Solaris, Linux and others these have names that end in .so, possibly followed by some numbers. On HP-UX, their names end in .sl. Etc.) Anyway, if you are user of Microsoft's compiler, why don't you ask them for help? Or why don't you ask on some of the umpteen Microsoft-oriented developer forums on the net? --tml |
From: Anirban Mazumder <anirban@ca...> - 2005-03-23 16:03:30
|
Hi, The link given was very nice. But my problem is something different. The problem is: Some of the dll files are already created in UNIX system (take any UNIX system). I need to convert them to Windows compatible dll files so that I can load those dll files and call the functions from MS VC++. Can any one please help in this regard with stepwise explanation? Thanks in advance. Anirban |
From: Daniel Raymond <danr@pc...> - 2005-03-23 15:30:12
|
> The trailing @number is not C++ decoration. It is actually > one of the things that __stdcall is for. The number is the > number of bytes passed to the routine so that the called > routine can clean the stack rather than the caller. Why would you want to do that? |
From: SourceForge.net <noreply@so...> - 2005-03-23 15:18:46
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3063306 By: poochner The trailing @number is not C++ decoration. It is actually one of the things that __stdcall is for. The number is the number of bytes passed to the routine so that the called routine can clean the stack rather than the caller. You can think of this as more 'extern "Pascal" {}' than anything else. It is the normal format for calls into the W32 API. If the library you are calling is not compiled that way, and it doesn't look it is, then there seems to be a mismatch between the headers and the lib. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=286529 |
From: Foster, Gareth <gareth.foster@si...> - 2005-03-23 14:53:26
|
That includes the autotools project, it's the tarball that "make dist" produces, I suppose I could just attach the important files (sizes included to differentiate files with the same name): / autogen.sh configure.ac Makefile.am (15 B) src/ Makefile.am (79 B) main.cc testcase.hh testcase.cc That misses all the GNU cruft that must be bloating the tarball. Let me know if I missed anything important. Cheers, Gaz > -----Original Message----- > From: Luke Dunstan [mailto:coder_infidel@...] > Sent: 23 March 2005 02:01 > To: mingw-users@... > Subject: Re: [Mingw-users] linker > > > ----- Original Message ----- > From: "Foster, Gareth" <gareth.foster@...> > To: <mingw-users@...> > Sent: Tuesday, March 22, 2005 11:28 PM > Subject: RE: [Mingw-users] linker > > > > Hopefully this will surfice, I trimmed out all the cruft > and left the > basics > > of what I am trying to do in terms of organisation, I then > ran "make dist" > > to produce a .tar.gz file (renamed with no extension so as > not to upset > > peoples' virus checkers etc) - is it okay to attach that > and send it to > the > > list (255 KB)? > > The limit for this mailing list is usually 140 KB. Is your > test case really > 255 KB with source code only (no object files or libraries)? > > Luke > > > > > You should get an error as below at the end of running > "./autogen.sh" when > > you try it. > > > > Sorry about the vagueness before. > > > > Regards, > > > > Gaz > > > > " > > g++ -g -O2 -o testcase.exe testcase.o main.o > > main.o(.text+0x5b): In function `main': > > u:/Code/testcase/src/main.cc:10: undefined reference to > > `nmspace_a::nmspace_b::testcase<char*>::testcase()' > > main.o(.text+0x94):u:/Code/testcase/src/main.cc:15: > undefined reference to > > `nmspace_a::nmspace_b::testcase<char*>::method(char*, char* const&)' > > main.o(.text+0xc7):u:/Code/testcase/src/main.cc:20: > undefined reference to > > `nmspace_a::nmspace_b::testcase<char*>::~testcase()' > > main.o(.text+0x109):u:/Code/testcase/src/main.cc:20: > undefined reference > to > > `nmspace_a::nmspace_b::testcase<char*>::~testcase()' > > make[2]: *** [testcase.exe] Error 1 > > make[2]: Leaving directory `/u/Code/testcase/src' > > make[1]: *** [all] Error 2 > > make[1]: Leaving directory `/u/Code/testcase/src' > > make: *** [all-recursive] Error 1 > > " > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile > Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs > or Smartphones > for the chance to win $25,000 and application distribution. > Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > MinGW-users mailing list > MinGW-users@... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > |
From: SourceForge.net <noreply@so...> - 2005-03-23 14:39:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3063220 By: dwondrousch Ah .. thx for these valuable informations According to your answers, I assume there is really no sysconf function in mingw ... Detecting the number of processors is just one job, sysconf could do ... but if there isn't such a function .. I'll have to do some workarounds ... So thx for your help ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=286529 |
From: Luke Dunstan <coder_infidel@ho...> - 2005-03-23 13:07:31
|
In future if you reply to a digest please fix the subject line and only quote the relevant parts. As several people have said, there are two answers to your question, depending on whether you have the source code for the Unix shared library. 1. If you have the source code, you must port it to Windows. This could be simple or difficult depending on the application. Using Cygwin would probably be easier if you can live with the restrictions. 2. If you have no source code, it is generally impossible. Even if you could do it with a lot of disassembly and hacking, it would not be very relevant to this mailing list. By the way, what does this library do? Luke ----- Original Message ----- From: "Anirban Mazumder" <anirban@...> To: <mingw-users@...> Sent: Wednesday, March 23, 2005 2:21 AM Subject: [Mingw-users] RE: MinGW-users digest, Vol 1 #2590 - 12 msgs > Hi, > The link given is very nice. But my problem is something different. > > The problem is: Some of the dll files are already created in UNIX system > (take any UNIX system). I need to convert them to Windows compatible dll > files so that I can load those dll files and call the functions from MS > VC++. > Can any one please help in this regard with stepwise explanation? > > Thanks in advance. > > Anirban |
From: Michael Gerdau <mgd@te...> - 2005-03-23 08:48:46
|
> I tried to link the C++ program with the Firebird library and found that = the > __stdcall declaration causes the compiler to generate the C++-decorated n= ames, > regardless the 'extern "C" {" ... '}' declarations in the header files. >=20 > for example >=20 > extern "C" > { > long __stdcall isc_vax_integer( > char *, short); > } // extern "C" >=20 > gives 'isc_vax_integer@...'. Removing __stdcall gives 'isc_vax_integer'. >=20 > Any ideas how to fix that? There is nothing to fix at all. 'isc_vax_integer@...' is *NOT* the C++-decorated name but exactly what is expected for __stdcall calling convention. To learn what the C++-decorated name looks like you could remove the extern "C" {} and see what you get (if you really wish to know). Best, Michael =2D-=20 Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mgd@... GPG-keys available on request or at public keyserver |
From: Luke Dunstan <coder_infidel@ho...> - 2005-03-23 02:01:25
|
----- Original Message ----- From: "Foster, Gareth" <gareth.foster@...> To: <mingw-users@...> Sent: Tuesday, March 22, 2005 11:28 PM Subject: RE: [Mingw-users] linker > Hopefully this will surfice, I trimmed out all the cruft and left the basics > of what I am trying to do in terms of organisation, I then ran "make dist" > to produce a .tar.gz file (renamed with no extension so as not to upset > peoples' virus checkers etc) - is it okay to attach that and send it to the > list (255 KB)? The limit for this mailing list is usually 140 KB. Is your test case really 255 KB with source code only (no object files or libraries)? Luke > > You should get an error as below at the end of running "./autogen.sh" when > you try it. > > Sorry about the vagueness before. > > Regards, > > Gaz > > " > g++ -g -O2 -o testcase.exe testcase.o main.o > main.o(.text+0x5b): In function `main': > u:/Code/testcase/src/main.cc:10: undefined reference to > `nmspace_a::nmspace_b::testcase<char*>::testcase()' > main.o(.text+0x94):u:/Code/testcase/src/main.cc:15: undefined reference to > `nmspace_a::nmspace_b::testcase<char*>::method(char*, char* const&)' > main.o(.text+0xc7):u:/Code/testcase/src/main.cc:20: undefined reference to > `nmspace_a::nmspace_b::testcase<char*>::~testcase()' > main.o(.text+0x109):u:/Code/testcase/src/main.cc:20: undefined reference to > `nmspace_a::nmspace_b::testcase<char*>::~testcase()' > make[2]: *** [testcase.exe] Error 1 > make[2]: Leaving directory `/u/Code/testcase/src' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/u/Code/testcase/src' > make: *** [all-recursive] Error 1 > " |