| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12
Comments:
<0> gcc -c $@ $?
<0> And for your .exe or whatever
<1> you could try man make :)
<2> using windows :(
<1> Bob77, :(
<0> Well it's certainly better than listening to threat
<1> Bob77, install cygwin?
<1> Ashe`, EAD
<2> Ashe : If i want to say in my main rule that in order to compile, you must have all the .cpp files converted to objects
<2> how do i do that ?
<3> What compiler are you using, Bob?
<1> ummm make %.obj as requirement ?
<2> g++ MinWG32
<0> Just like all the .obj's you need
<3> Then I think you can use makefiles.
<4> Greetings,
<3> Whytf is google and tvguide so slow
<1> whitewabbit, werd
<0> JBlitzen: if he was not using it he wouldn't be asking about makefile rules
<3> http://www.mingw.org/mingwfaq.shtml#faq-Makefile
<3> Oh
<5> Bob77 %.obj: %.cpp
<4> hi threat, JBlitzen, Ashe, others,
<3> Yeah, I wondered about that
<2> danke
<4> hey vawjrwrk
<5> that's the rule
<1> whitewabbit, sup?
<5> then put the compile on the next line
<1> Bob77, uber danke!
<0> I guess you have to tell Bob77 3 times the same thing until he gets it
<4> threat, same o samo, but doing all right, yourself mate ?
<3> [18:10] <1> you could try man make :)
<3> [18:10] <2> using windows :(
<3> misread ^
<5> then again, there already IS a rule like that in make
<4> lol
<5> actually you want to get the 100+ page GNU make manual
<0> http://img445.imageshack.us/img445/1294/01311sz1i99118007lm.jpg
<1> whitewabbit, nadda much
<4> threat, enjoy your day/evening man, it's nice to be around w/ you and the others.
<2> i was looking for this OBJ=$(SRC:.c=.o)
<1> whitewabbit, indeed
<6> Bob77, you shouldn't use make, but automake instead
<3> *paste*
<3> 8 48 ms * 48 ms tbr1-cl6.sl9mo.ip.att.net [12.122.10.89]
<3> 9 47 ms 47 ms 47 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
<3> 10 47 ms * 47 ms tbr2-cl27.wswdc.ip.att.net [12.122.9.150]
<3> 11 * 47 ms 47 ms tbr2-cl15.n54ny.ip.att.net [12.122.10.53]
<3> 12 * 45 ms * 12.122.81.145
<3> 13 48 ms 48 ms * mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122
<3> .162]
<3> 14 48 ms * * sccsbix12-1-4.attbi.com [63.240.64.46]
<3> What do we think of this tracert
<7> ****ed up?
<2> option B ?
<8> ?
<0> On my "personal server at work" (don't ask), I had routing problems cause I mistyped a name in /etc/hosts :'(
<8> is there anything we're supposed to think?
<0> Basically there's a failover between two interfaces, and a failover between cluster members
<0> And I mistyped the name for the first failover
<0> So the second interface was routed through the first one
<5> gribouille you and Run should get together, you're the only people I've ever heard who recommend automake
<5> and it make ****ty make files
<0> => when the second one was active and you disconnected the first one, no more connection :(
<5> err, and it makes
<0> (I looked at etc/hosts about 10 times before finally noticing)
<3> Heh
<3> I dunno, it just seems like there are a lot of *'s in there
<6> vawjrwrk, what do you use instead of automake ?
<9> nigga killa 101
<0> vi or notepad? heheh
<9> vawjrwrk is a hard***
<1> JBlitzen, I think you just spamed the **** out of this channel
<9> JBlitzen is oper what?
<3> Well, too bad
<9> o-lines rock
<5> gribouille I make them with an editor
<6> vawjrwrk, you mean you write your own makfiles ?
<0> I write my own makefiles too
<5> that's what I just said, yes
<0> Not like it takes much time
<6> vawjrwrk, that's nonsense
<5> gribouille why?
<7> They're probably not very portable.
<0> Works on at least 10 platforms, so must be a least a little bit portable
<0> A compiler command line is rarely non portable
<6> vawjrwrk, becuse it is extremely tedious to do, and because there are good and ubiquitous tools that do it for you
<5> gribouille bull****
<5> it's not tedious to do at all
<5> what could POSSIBLY make writing a makefile tedious
<6> vawjrwrk, for a small project, it can be feasible, but not for lage projects
<0> It's only 400k lines
<0> Heheh
<0> And at work it's like 3 millions
<0> But it's not feasible for sure
<5> gribouille ok, what makes it tedious for large projects?
<5> we use the same options for each type of file
<5> make calls itself just fine to handle multiple directories
<5> dir
<6> vawjrwrk, why did some people bother to write the autotools if they are not necessary ?
<5> I guess they wanted to **** around
<5> or they were stuck w/ the original make
<0> Like every software is necessary
<5> unix make really really ****ed
<5> GNUmake is a rather nice program
<6> vawjrwrk, if you write you own makefile, it is likely not to be portable
<5> and?
<5> you think it's rocket science to change for a new compiler?
<0> Must be, if people wrote autotools
<6> vawjrwrk, if you can avoid it, why not ?
<5> I can guarantee you one thing, automake isn't ****ing portable
<0> Or maybe it's just for people who don't understand much about what they're doing
<5> because automake doewsn't run worth **** on windows
<5> ask Run about trying to get a project going that I was gonna test for him..... HOURS of config and automake **** and it kept blowing up
<7> windows is not worth supporting anyway
<7> heheh
<5> but it ran perfectly on his *nix system
<0> (and then they babble about portability)
<5> Ashe` actually they NEED portability due to all the weirdnesses in the different *nixes
<7> I tried once to write something that runs on both linux and windows, and I gave up. They are too different.
<0> I write something that runs in both linux and windows
<5> my **** runs w/ no problems...but then I stick to standard C or C++
<0> But also BSD, MacOS X, Xbox, gamecube, etc
<0> And somehow I have a single makefile
<0> And it's quite small
<7> Hello World?
<0> Yes, 400k worth of hello world
<0> (lines, that is)
<5> Ashe` any includes in it? (that's how we did our differing platform stuff generally)
<7> Is it open source?
<0> Run: nope
<0> vawjrwrk: what do you mean?
<0> (because of course I have headers heh)
<5> well, we had a bunch of environment variables we'd put in a separate file to be included in the make file (locations of the includes, libraries, etc) so we could have a single GNUmakefile which would run on any system that we'd set up the compiler system (and the inc'd makefile" on
<5> yeah, I guess headers is a good name for them also
<0> Ah, yes I define some variables separately
<0> But it's just compile name and flags
<0> Not many
<0> +r
<0> It's not even a "translation" of the flags, actually
<5> shocked the hell out of the guys in Florida when I went there.... rewrote the make files for gnumake and then started using -j
<5> build ran in 10 minutes instead of 1.5 hours
<5> of course it used all 26 processors in the machine, but what the hell
<0> I have to build on my poor bi-xeon :'(
<0> At work it's a small cluster with 8 CPUs
<6> vawjrwrk, why doesn't automake work on windows
<6> ?
<5> they had a 26-way solaris machine for doing the *nix builds
<0> It's solaris too
<0> But 2x 4-way
Return to
#c++
or
Go to some related
logs:
12WHAT ROBERT LOUIS STEVENSON ADVENTURE FEATURES THE SHIP CALLED COVENANT?
#php
fdreopen
#teens
_pango_cairo_font_map_get_renderer
#linuxhelp
Shared object libssl.so.3 not found
#chatzone
CAPCAPLI
#AllNiteCafe
|
|
