Lcc-Win32 Support Group
Coordinated by: Waxhead & BJTHR

- The group is an independent community of users wanting to put forward the development and improvement of lcc-win32

> Updated:07. October 2006 <


Hi and welcome to the Lcc-Win32 support group!

The Lcc-Win32 support group is a apooved independent cooperation of Lcc-Win32 enthusiasts who are constantly trying to improve and support the Lcc-Win32 project in various ways. The support group original goal was to collect the most popular feature requests and getting them implemented in LccWin32 by letting the support group's members cover the developement cost as if they where one single person. This would help making the developement cost for a particular feature acceptable, since one individual didn't have to pay for a custom feature on his own, but rather share the cost with the rest of the Lcc-Win32 support group members.

The support group are currently focusing on information and support for the Lcc-Win32 community. The coordinators roles are mainly to organize and present the information to the members, and to maintain contact with the QSS' team on behaf of the support groups members.

Feel free to join us in a discussion at the support group forum or the wiki hosted by QSS.


Tutorials / References

The Forgers Win32 API tutorial (very good one!) http://winprog.org/tutorial/
A must for winblows ;) programming http://msdn.microsoft.com/
Binary manipulation http://www.gmonline.demon.co.uk/cscene/CS9/CS9-02.html
C language tutorial
http://www.physics.drexel.edu/courses/Comp_Phys/General/C_basics/c_tutorial.html
C language tutorial (another one)
http://www.lysator.liu.se/c/bwk-tutor.html
Sockets programming
http://beej.us/guide/bgnet/output/html/intro.html
The elements of C style (code layout etc...)
http://www.teamten.com/lawrence/style/
C for smarties (Just in case you didn't understand it's not for beginners ;) )
http://web.torek.net/torek/c/index.html
Robust design techniques for C programs
http://www.freetype.org/david/reliable-c.html

Snippets and resources

Literate programs
http://en.literateprograms.org
Code snippets
http://www.johnfindlay.plus.com/lcc-win32/index.html
C Scene
http://www.gmonline.demon.co.uk/cscene/
Code guru
http://www.codeguru.com/
Programmers heaven
http://www.programmersheaven.com/
The Code project
http://www.codeproject.com/
Devmaster ( a site for game programming )
http://www.devmaster.net/

Audio related

OpenAL - Portable audio
http://www.openal.org/



Graphics related

OpenGL - Portable graphics
http://www.opengl.org/



Beginners

C language
Nothing here yet
Windows
Nothing here yet (http://winprog.org/tutorial/)
Quickguide: C language basics
Nothing here yet
Quickguide: Making a project in WEdit
Nothing here yet
Quickguide: Compiling using command line
Nothing here yet

Miscellaneous / Uncategorized


Free C stuff
http://www.thefreecountry.com/sourcecode/cpp.shtml
OpenGL stuff and more
http://nehe.gamedev.net/
Sourceforge
http://www.sourceforge.net/
The Open Source initiative
http://www.opensource.org/docs/definition_plain.html
Home of Inno setup - Make installers for your programs (very good one!)
http://www.jrsoftware.org/isinfo.php
GNU's not Unix, The GNU project and the Free Software Foundation http://www.gnu.org/fsf/fsf.html
NetLib home page - a repository of mathematical software, data, documents, address lists, and other useful items http://netlib.bell-labs.com/netlib/master/readme.html
RFC Editor Home Page http://www.rfc-editor.org/
WebRing C/C++ rings (Borland stuff, Forums, etc.) http://dir.webring.com/rw?d=Computers___Internet/Programming_Languages/C_and_C__
Current news about Computer/Net-Security http://www.securityfocus.com/

Miscellaneous / Uncategorized - Non-English sites


C/C++ forum http://www.c-plusplus.de/forum
A developers forum (mostly in German) http://www.entwickler-forum.de
intitute for legal issues of free and open source software (German)
http://www.ifross.de/



Did you know that...
Open a file, write some code and then press F9 builds a default project
The default project in your projects folder can be used for testing quick snippets of code
Pressing ESC autocompletes a structure or other info.
Handy if you disable automatic structure completion. You can always just press ESC to get suggestions.
How to insert / remove a Icon in the resource editor
use the keys INSERT and DELETE on your keyboard
To reduce the size of compiled code

The code to the right dynamically links with windows's crtdll.dll instead of statically linking with LccWin32's runtime (to save space)
Warning: you can't use the C99 additions to printf; for example %lld for long longs


this code is by Jacob Navia and is taken form the QSS forums

#include <windows.h>

#include <stdio.h>

void __defaultTrapHandler(int code)
{
  char buf[256];

  strcpy(buf,"Exception 0x");
  itoa(code,buf+strlen(buf),16);

  MessageBox(0,buf,"lcc runtime",MB_OK);
  abort();
}

int main(void)
{
  printf("hello\n");
}


compile with: lc hello.c -nolibc

Or add -nolibc as a linker argument in WEdit

Tutorials (not available yet)
Getting started
Nothing here yet....
Building your first console application
Nothing here yet...
Building your first win application
Nothing here yet...



Also check out:
   lccwin32 forum
   Feature request list

History:
As mentioned earlier the original goal of the support group was to work as a single indivudual to get features implemented. The basic principles was as follow:
- Gather a list of features
- Vote for features
- Vote again for the feature requests that had the most votes
- Pick the feature with the most votes and get a rough price estimate for implementing that particular feature.
- Confirm participation from each member
- Each member pay QSS and notifies that the payment is for a particular feature (idnumber).

Since the LccWin32 communiy is based on trust each member shoul be responsible for making sure their money recieved QSS in their way. There is no point in choosing a special person to collect the money since there are no refunds. All extras or funds collected for a particular feature will be "transfered" to the next feature request in line if the first one was impossible to implement.
The support group was to keep statistics over the recieved funds and the amount required to start implementing features. If some members for some reason did not participate it would be up to the rest of the members to raise the neccesary funds to cover for the shittbag who dropped out ;)