Acc.exe SVN builds...
Moderator: Dev Builds Team
- Remmirath
- DRD Team Admin (Inactive)
- Posts: 528
- Joined: Fri Feb 15, 2008 19:43
- Location: Somewhere...
- Contact:
Acc.exe SVN builds...
I don't know if this is the correct place, but i remember that when Nash was maintaining the SVN service, he was also hosting svn copies of acc.exe...
Can it be possible to host this service here too?
Can it be possible to host this service here too?
SoulPriestess wrote:Good job, Morpheus! You are teh awesum!
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
I would happily compile ACC if someone could step me through how to do it. I just checked out the SVN and tried to compile it. I got an executable that seems to run but I got a bunch or warnings when I did it so I assume that I'm doing something wrong. Remember, I'm still pretty new at this compiling lark.
When I load it into Visual C++ I get told that "The source control provider associated with this solution could not be found. The projects will be treated as not under source control."
and I get all these when I hit the compile button
[spoiler][/spoiler]
When I load it into Visual C++ I get told that "The source control provider associated with this solution could not be found. The projects will be treated as not under source control."
and I get all these when I hit the compile button
[spoiler]
Code: Select all
Compiling...
token.c
.\token.c(308) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\token.c(315) : warning C4996: 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(79) : see declaration of 'strcat'
.\token.c(345) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\token.c(346) : warning C4996: 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(79) : see declaration of 'strcat'
symbol.c
.\symbol.c(414) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
strlist.c
.\strlist.c(110) : warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(157) : see declaration of 'strncpy'
.\strlist.c(246) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
pcode.c
.\pcode.c(481) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\pcode.c(1490) : warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(157) : see declaration of 'strncpy'
parse.c
.\parse.c(3897) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
misc.c
.\misc.c(150) : warning C4996: 'open': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _open. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\io.h(328) : see declaration of 'open'
.\misc.c(164) : warning C4996: 'read': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _read. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\io.h(329) : see declaration of 'read'
.\misc.c(165) : warning C4996: 'close': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _close. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\io.h(318) : see declaration of 'close'
.\misc.c(185) : warning C4996: 'open': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _open. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\io.h(328) : see declaration of 'open'
.\misc.c(190) : warning C4996: 'write': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _write. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\io.h(334) : see declaration of 'write'
.\misc.c(191) : warning C4996: 'close': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _close. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\io.h(318) : see declaration of 'close'
.\misc.c(274) : warning C4996: 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(79) : see declaration of 'strcat'
error.c
.\error.c(263) : warning C4996: 'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\stdio.h(234) : see declaration of 'fopen'
.\error.c(359) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\error.c(362) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\error.c(366) : warning C4996: 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(79) : see declaration of 'strcat'
acc.c
.\acc.c(206) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\acc.c(210) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\acc.c(224) : warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\string.h(74) : see declaration of 'strcpy'
.\acc.c(252) : warning C4996: 'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
F:\Program Files\Microsoft Visual Studio 8\VC\include\stdio.h(234) : see declaration of 'fopen'
Generating Code...
Linking...
Embedding manifest...
- Rachael
- Developer
- Posts: 3645
- Joined: Sat May 13, 2006 10:30
Looks like it compiled fine to me. Those messages were just warnings. I know, it's weird, it does that on my system too.
You can turn off warning generation, it's in the individual project's settings. I would only ever do it under "release", though. Those warnings are handy if you ever need to make any code changes.
What these warnings are saying, is your project pretty much is not .NET compliant, and it's trying to tell you how to make them so.
You can turn off warning generation, it's in the individual project's settings. I would only ever do it under "release", though. Those warnings are handy if you ever need to make any code changes.
What these warnings are saying, is your project pretty much is not .NET compliant, and it's trying to tell you how to make them so.
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
- Rachael
- Developer
- Posts: 3645
- Joined: Sat May 13, 2006 10:30
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
OK, I've put my build of ACC up. I've tested it with a few of my scripts and it seems to work just fine. I've used the same naming convention as the other builds. ACC currently reports as r1228 when you use TortoiseSVN but it only does so because that's the current Zdoom revision number. Internally, ACC only reports itself as 1.46. It would be pointless to upload a build of ACC every time the Zdoom revision number changes so I'll just keep an eye on it and when something changes with ACC, I'll upload a build using whatever the revision number at the time is.
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
Thinking about it, I was wondering how useful SVN ACC builds are. Has there ever been a time when the SVN version of ACC was out of step with the official version posted on Zdoom?
As far as I am aware, ACC occasionally gets a change made to it and, when that happens, Randy compiles a new version and puts it online. Is that not the case? I can't remember a time where people were desperately waiting for an official release of ACC so that they could use some feature that was in the SVN version.
As far as I am aware, ACC occasionally gets a change made to it and, when that happens, Randy compiles a new version and puts it online. Is that not the case? I can't remember a time where people were desperately waiting for an official release of ACC so that they could use some feature that was in the SVN version.
- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
- MartinHowe
- Posts: 154
- Joined: Tue Aug 30, 2005 22:07
- Location: Waveney, United Kingdom
The CRT SECURE and POSIX NAME stuff is Microsoft deprecating half the standard C libraryEnjay wrote:and I get all these when I hit the compile button
The former is because many C Runtime Library (CRT) routines take a memory address but no size, thus making it impossible for the routine to check for buffer overflows. The latter is because of POSIX naming conventions being different to normal C conventions.
Something like this needs the support of the whole C community, not Microsoft unilaterally imposing it on everybody and if you're compiling mature legacy C code without intending a near-complete rewrite, it just gets in the way, as such programs should by now make calls to the CRT with valid buffers. Of course, the biggest offender was probably the Windows source code, hence the many IE exploits
In MSVC, disable warnings 4995 and 4996 to suppress these.
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
I've just uploaded a new build of ACC (r1311) However, it still appears to have the bug.
http://forum.zdoom.org/viewtopic.php?f=2&t=19881
The only reason to DL and try 1311 would be if you want to give this new feature a go:
http://forum.zdoom.org/viewtopic.php?f=18&t=20040
If you don't want to play around with that, stick with the older version as it is more likely to be able to compile your scripts.
http://forum.zdoom.org/viewtopic.php?f=2&t=19881
The only reason to DL and try 1311 would be if you want to give this new feature a go:
http://forum.zdoom.org/viewtopic.php?f=18&t=20040
If you don't want to play around with that, stick with the older version as it is more likely to be able to compile your scripts.
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
In this thread over at Zdoom
http://forum.zdoom.org/viewtopic.php?f=7&t=20771
Graf mentioned that compiling ACC with Visual C++ 2005 is not exactly ideal and that running the compiled binary requires a certain DLL that comes with VC++ 2005 and some other programs but which most people won't have.
I'm not really in a position to install MiniGW ATM so I would like to know if people consider me continuing to build binaries with VC++ 2005 worthwhile.
So, are people downloading an using my compiled ACC files or is it a pointless exercise?
The most recent upload at this time contains the binary built by Graf and should therefore be fine.
http://forum.zdoom.org/viewtopic.php?f=7&t=20771
Graf mentioned that compiling ACC with Visual C++ 2005 is not exactly ideal and that running the compiled binary requires a certain DLL that comes with VC++ 2005 and some other programs but which most people won't have.
I'm not really in a position to install MiniGW ATM so I would like to know if people consider me continuing to build binaries with VC++ 2005 worthwhile.
So, are people downloading an using my compiled ACC files or is it a pointless exercise?
The most recent upload at this time contains the binary built by Graf and should therefore be fine.
- Rachael
- Developer
- Posts: 3645
- Joined: Sat May 13, 2006 10:30
Enjay, yes, people are downloading your ACC builds, according to the site log.
I haven't checked the log thoroughly, but there are at least 16 unique hits against the .zip files just last week alone, and tons more of people checking the directory itself (presumably, to see if it's been updated).
If you want, I can try and see if I can add a stat tracker for you. Most of the hits on the SVN site are probably just people checking to see if anything's been updated, though. I'd say 1 in 4 visits ever get an actual download.
I haven't checked the log thoroughly, but there are at least 16 unique hits against the .zip files just last week alone, and tons more of people checking the directory itself (presumably, to see if it's been updated).
If you want, I can try and see if I can add a stat tracker for you. Most of the hits on the SVN site are probably just people checking to see if anything's been updated, though. I'd say 1 in 4 visits ever get an actual download.
- Enjay
- Developer
- Posts: 4723
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
OK, well given that it really isn't a problem for me to build and upload ACC, I'll keep doing it unless there is a good reason not to.
Agent ME over at Zdoom has said that he had problems running my Visual C build but if the files are getting the kind of downloads you say they are, it's reasonable to assume that they are of use to someone otherwise there probably would have been more "it doesn't work" feedback. I'll maybe add a warning to the header file to make people aware of the situation.
[edit] Header file changed and Graf's build renamed to tie in with what the header says. [/edit]
Agent ME over at Zdoom has said that he had problems running my Visual C build but if the files are getting the kind of downloads you say they are, it's reasonable to assume that they are of use to someone otherwise there probably would have been more "it doesn't work" feedback. I'll maybe add a warning to the header file to make people aware of the situation.
[edit] Header file changed and Graf's build renamed to tie in with what the header says. [/edit]