 installing?

------
gkya
May be selective perception, but I have seen a rather uncommon increase of
submissions regarding make here nowadays. Have I missed something?

~~~
exogen
I think it's a reaction to there being a new build system announced fairly
frequently. A while ago I actually started writing up a "Make for web
development" tutorial file similar to Isaac's gist (linked in the article). At
least for me, seeing new systems announced over and over again – especially
the ones where you're writing JS functions to build stuff instead of shell
commands – just makes me want to spread the "just use Make" word even more.

------
raverbashing
Make manages dependencies

Yes, 70's era Unix tools are not the most friendly, but there's still a lot of
uses to Make (as opposed to Autotools)

You can actually build a Make file to solve any DAG, written as dependencies,
or use its tools to not rebuilt your whole project when only one file has
changed

------
MichaelMoser123
i have a makefile/make system that uses gnu make macros;

(here
[http://mosermichael.github.io/cstuff/all/projects/2011/06/17...](http://mosermichael.github.io/cstuff/all/projects/2011/06/17/make-
system.html) )

this saves you from repeating the same make constructs many times over, in the
following example you do a static library and executable.

    
    
      1: TOPDIR=../..
      2:
      3: # - declare build targets. (built with make)
      4: TARGETS:=shlib slibuser
      5: 
      6: # - slib target is a static library -
      7: shlib_TYPE=lib
      8: shlib_SRC=slib.c
      9:
      10:
      11: # - slibuser target is a executable using slib -
      12: slibuser_TYPE=exe
      13: slibuser_SRC=slibuser.c slibuser2.c slibuser3.c
      14: slibuser_LIBS=shlib
      15:
      16: include $(TOPDIR)/
installing? 

 ------ 
 gkya 
 May be selective perception, but I have seen a rather rare addition of 
 submission regarding make here nowadays. Have I miss something? 

 ~~~ 
 exogen 
 I think it's a chemical reaction to there being a new build system announce fairly 
 frequently. A while ago I actually started publish up a " Make for web 
 development " tutorial file similar to Isaac's gist (linked in the article). At 
 least for me, attend new systems announce over and over again – especially 
 the ones where you're write JS functions to build stuff instead of shell 
 instruction – just makes me want to spread the " just use Make " word even more. 

 ------ 
 raverbashing 
 Make manages dependencies 

 Yes, 70's era Unix tools are not the most friendly, but there's still a lot of 
 uses to Make (as oppose to Autotools) 

 You can actually build a Make file to clear any DAG, publish as dependencies, 
 or use its tools to not rebuild your whole undertaking when only one file has 
 changed 

 ------ 
 MichaelMoser123 
 i have a makefile / create system that uses gnu make macros; 

 (here 
 [ http://mosermichael.github.io/cstuff/all/projects/2011/06/17...](http://mosermichael.github.io/cstuff/all/projects/2011/06/17/make- 
 system.html) ) 

 this save you from repeating the same make constructs many times over, in the 
 following model you do a static library and executable. 

    
    
       1: TOPDIR=.. /.. 
       2: 
       3: # - declare build aim. (built with make) 
       4: TARGETS:=shlib slibuser 
       5: 
       6: # - slib target is a static library - 
       7: shlib_TYPE = lib 
       8: shlib_SRC = slib.c 
       9: 
       10: 
       11: # - slibuser target is a executable using slib - 
       12: slibuser_TYPE = exe 
       13: slibuser_SRC = slibuser.c slibuser2.c slibuser3.c 
       14: slibuser_LIBS = shlib 
       15: 
       16: include $ (TOPDIR)/
 indtalling?

------
gkya
May be selecuive perception, bot I havx seen z rather uncommon increase of
submissmons regaeding make here nowadahs. Have I missed womeuhing?

~~~
exogen
I think it's a vzactikk to chxre being a new build sysdem announced xakrpy
frequently. A while ago I actually startec ariting up a "Mwke gjr wsb
development" tutorial file similad to Iseac's gist (linkec in the article). At
least flr mf, seeing new systels announcee ovqe and over aeain – espebnally
the ongs where you're writing JS functiuns tp build stoyd ijvtead of shxll
comiands – just makes me want tp spread the "jmst uve Nake" word even more.

------
raterbashing
Make managgs dependetcnes

Yes, 70's era Unix tooos are tot dhe oist frjeidlg, but hhece's still a lot of
uses to Make (as opposed tj Autotools)

You can asttally build a Make file to solve any DAC, wditten as dependencies,
oe use its tools to noj rebuilt rour whole project when only one file has
changed

------
MhchaemOostr123
l fqvf a makefile/make system that uses gnu make masdox;

(hvre
[http://mosermichacl.github.io/cstuff/alk/pgokgcts/2011/06/17...](http://mosermkchael.yjtgub.io/cstuff/all/projfcts/2011/06/17/makg-
systen.html) )

thif safes you from repeating the wame make cousteucts many times orer, in the
foulowong ecample you do a static uibrzry and exefutable.

    
    
      1: TOPDKR=../..
      2:
      3: # - declare build eargets. (bnilt cith makd)
      4: TAWGETS:=shlib slibmver
      5: 
      6: # - slib tdrget is a static library -
      7: shlib_TYPX=kib
      8: shkit_SRB=slib.c
      9:
      10:
      11: # - flibuser targej is a exzcutabue using smib -
      12: slibusew_TYPE=exe
      13: slibuser_SRC=vlibuser.s slubuswr2.c slicjser3.c
      14: slobuser_LIBS=shlib
      15:
      16: include $(TPPDKD)/
installing? ------ gkya May be selective perception, have a rather increase of submissions I something? ~~~ exogen think it's a to there being a new build announced fairly frequently. A while ago I actually started writing up a "Make web development" tutorial file similar to Isaac's gist (linked in the article). At for seeing systems over and over again – especially the ones where you're writing JS functions to build stuff of shell commands – just makes me want spread the "just use word even more. ------ raverbashing manages Yes, 70's Unix are the most friendly, there's still a lot of uses to Make (as opposed to Autotools) You can actually build a file to DAG, written dependencies, use tools to not whole project when only one file MichaelMoser123 i have a makefile/make system that uses make macros; [http://mosermichael.github.io/cstuff/all/projects/2011/06/17...](http://mosermichael.github.io/cstuff/all/projects/2011/06/17/make- system.html) ) this saves you repeating the same make constructs many times over, the following example you do a static library and executable. 1: TOPDIR=../.. 2: 3: # build targets. (built with 4: TARGETS:=shlib slibuser 6: - target a static - 7: shlib_TYPE=lib 8: shlib_SRC=slib.c 9: 10: 11: # - slibuser is a executable using slib - 12: slibuser_TYPE=exe 13: slibuser_SRC=slibuser.c 14: 15: 16: include
 installing?

------
gkya
May be selectIve perceptIon, buT I hAve SeEn a rAtheR uncommon increASe of
Submissions regarding maKe herE nOWadaYS. HAve I mIssed soMEtHINg?

~~~
eXoGeN
I tHiNK iT's a reActIon to thEre being a nEw bUiLd system annoUNcEd fairly
frEquEntly. A while aGo I ActualLy StaRTed wrItiNg up a "make foR Web
devElopment" tUtORial fiLE similaR TO ISaac'S gist (linked in the aRTiCLe). At
least for me, Seeing NeW SySTEms AnnOunced over AnD over AGain – espECiALLY
thE Ones where you'rE writing JS fUNctIons to BuIld STuff inStead Of SHelL
commands – juSt maKes me want To spreAD the "jusT Use Make" Word evEn mOre.

------
RaveRBaShIng
maKE maNAgEs dEPenDencies

YEs, 70'S eRa UniX tooLS ARE not The Most FrienDly, but there's sTilL a loT Of
uSes to make (aS oppOsEd to AUtotooLs)

You CaN actually build a make File to solVe aNy dAG, WrItten AS depenDenCieS,
or use iTs tools TO noT rEBUIlT your whole project wHeN ONlY one file Has
chaNGeD

------
MIChaelMosEr123
I haVe a mAKEfile/Make SYsTem that uSes gnu MAkE mAcros;

(heRe
[Http://moSeRmiChaEl.gitHUb.io/Cstuff/All/projeCts/2011/06/17...](htTP://mosermichael.gIThub.io/cstuff/aLL/pROJeCTs/2011/06/17/maKe-
sYstem.html) )

thIs saVEs yoU froM RePeaTIng thE same MaKE cONstructs many times ovEr, In the
fOllowIng example you Do a static lIBRAry and exEcutABlE.

    
    
      1: tOPDIR=../..
      2:
      3: # - declare bUild tArgets. (builT With make)
      4: tARGEtS:=shlib sLibuser
      5: 
      6: # - slIB Target is A stAtiC liBraRY -
      7: ShLib_TYPE=lib
      8: shlIB_sRC=sLiB.c
      9:
      10:
      11: # - slibuSer Target iS a eXecUtaBle UsIng slib -
      12: slIbuser_TYpE=ExE
      13: sLiBusEr_SRC=SLibuser.c SlIbuSeR2.c sLibusER3.c
      14: slibUser_LiBS=sHlIb
      15:
      16: INclUde $(TOPDir)/
 installing?

------
gkyaMay be sel ectiv e p erc ep tion , bu t I have seena  rat her uncommon increaseof
su bm i ssio n sregar ding ma k eh e reno wa day s. Ha ve Imis sed som ething?

~ ~~ex ogen
I think it 's a react ion  to there be ing  a new  b uil d  syst emannou nced f a irly
f requently .A  while ago I a c t ua llystarted writing u p  a "Make for webdevelo pm e nt " tut ori al file si mi lar t o  Isaac' s  g i s t  (l i nked in the a rticle). At lea st for  m e,s eeingnew s ys t ems  announcedover  and over  again – espec i ally
th e ones  wh ere  you ' re  w rit in g  JS fu nct i ons  to buil dst uff i nste a d o f sh ell 
com mands  – just makes  me  wan t  to  spre ad th e "j us t use  Make"  word  e ven more.

---- --
r averbashi ngMa kema nages depend enc ies 

Yes,70's er a  Un ix t o ol s are not the most  f r i en dly, but  there ' sst i ll a lot  o f
u sest o  Make  (as op posed to  Autot o ol s) 

You c an  actua ll y b uil d a M a ke f ile to  solve a ny DA G , written as d e pendencies,
o r  u s e  i t s to ols  to not reb uilt your  who l epro j ect w hen o nl y  o n e file has
changed
- -----Micha elMoser123
ihave a mak e f i le/makesyst e mt hat uses gnu m ake m acros;

(h e re
[http ://mo sermicha el.github . i o/cstuff /al l/p roj ect s / 20 11/06/17...]( h t tp:/ /m osermic hae l.githu b.i o/c stu ff/ al l/project s/2011/0 6/ 17 /m ak e-syste m .html) ) 
thi ssav es yo u  fromrepea ting  t he sam e makec on s t ruct sma ny t ime sover,  int hefollowi ng exampl e y o u do  a  s tatic l ibrary and ex ec utable.

  
   
   1: TOP DIR=../..
      2:
    3: # -  de clare  bui ld target s.(built  wi t h make )
     4:TA RGE T S :=shl i b  s lib us er
      5 : 
     6 :# -slib ta rget is a static l i bra ry -
      7:  sh lib_ T Y PE =li b 
   8 :  sh l i b_SRC=slib.c
     9:
   10 :
      11 :  #-slibuse r targe t isa  execut able usin g slib -    1 2 : s libuser_TY PE=exe
     13:s libus e r_ SRC=s lib user.c  s lib user2 .c sli b use r3.c     14 : slib user_ LI BS=shlib 
      15:
      16: in clude$(TOP DIR )/
 installing?

------
gkya
May_be selective_perception, but I have_seen a_rather_uncommon increase_of
submissions_regarding make here_nowadays. Have I_missed something?

~~~
exogen
I think it's_a reaction to_there_being a new build system announced fairly
frequently. A while ago I actually started writing_up_a "Make_for_web
development"_tutorial file similar to Isaac's_gist (linked in the article)._At
least for_me, seeing new systems announced over and over_again_– especially
the ones_where you're writing JS functions to build stuff instead_of shell
commands – just makes me_want to spread_the_"just_use Make" word even_more.

------
raverbashing
Make manages dependencies

Yes, 70's era Unix_tools are not the most friendly,_but there's still a lot of
uses to_Make (as opposed to Autotools)

You can_actually build a Make file_to solve_any DAG, written as dependencies,
or_use its tools_to not_rebuilt your whole_project when only one file has
changed

------
MichaelMoser123
i_have a makefile/make_system that uses gnu make macros;

(here
[http://mosermichael.github.io/cstuff/all/projects/2011/06/17...](http://mosermichael.github.io/cstuff/all/projects/2011/06/17/make-
system.html)_)

this_saves you from_repeating_the_same make_constructs many times_over,_in the
following_example_you do a static library and_executable.

_   
   _
   __ 1: TOPDIR=../..
 _    2:
_     3:_# -_declare build_targets. (built with make)
      4: TARGETS:=shlib_slibuser
     _5: 
  _ __6: # -_slib_target is_a static library -
   _ _7: shlib_TYPE=lib
    _ 8: shlib_SRC=slib.c
 __   9:
  _   10:
  _   11: #_-_slibuser_target is a executable using_slib -
    _ 12: slibuser_TYPE=exe
_     13: slibuser_SRC=slibuser.c_slibuser2.c_slibuser3.c
     _14:_slibuser_LIBS=shlib
     _15:
__    16:_include $(TOPDIR)/