Indeed. I like TCC so I want to help keep the faith. Sometimes I really might need the answer even after weeks of fumbling around, so if I can help spare anyone that it might increase my chances too. I don't know enough to contribute much more. :)
Milutin_Jovanovic <[email protected]> wrote: (17/02/2012 02:40) >I am glad to see you found a solution. As you can see this is not the most >active of projects/mailing lists, so it is a hit and miss. I am sure >somebody would have answered if they knew. Thank you for posting your >solution here. It will surely help someone who searches for this in the >future. > >Miki. > >On 16 February 2012 14:45, Lostgallifreyan <[email protected]> wrote: > >> Well, I was very kindly answered by 'nobody' (and myself a couple of >> times) but nobody didn't have anything to say so I eventually found a way >> myself. >> >> In case anyone comes by wanting the answer, it's this: >> tiny_impdef.exe C:/Windows/System/Winmm.dll >> (tiny_impdef.exe is supplied with TCC) >> Put the resulting WINMM.DEF file into the TCC's lib directory. After which >> this works: >> >> TCC.EXE C:\WINDOWS\DESKTOP\TEST\MIDI.c -lwinmm >> -oC:\WINDOWS\DESKTOP\TEST\MIDI.exe >> >> (Do not use '-Lwinmm.def', use LOWER case -l, and omit the .def bit or it >> still borks.) >> >> I still don't know why we can't do it with the same command we'd use for >> GCC, but it this price of inconvenience pays for the ability to fetch >> definitions from ANY dll file so we can call its functions for code >> compiled with TCC, it's a neat idea that I can live with. >> >> >> _______________________________________________ >> Tinycc-devel mailing list >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/tinycc-devel >> > > > >-- >Miki. _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
