1. Forum
  2. DOVE-Net
  3. Synchronet Discussion

  • Cleaning the Source Tree

    From Apam@VERT/NOCTURN to All on Friday, July 12, 2019 17:46:08
    Hi

    I'm probably missing something obvious, or theres something in the wiki I missed...

    When updating via cvs, how dows one delete all the build directories? When I updated this afternoon, I did it manually, but there seem to be a few of them in different subdirectories..

    I guess I could make a script to find all the clang.freebsd.amd64.* folders and delete them, but I wanted to check if there was a recommended way?

    Andrew

    ---
    þ Synchronet þ Nocturnal - nocturnal.hopto.org:2023
  • From Nightfox@VERT/DIGDIST to Apam on Friday, July 12, 2019 09:24:10
    Re: Cleaning the Source Tree
    By: Apam to All on Fri Jul 12 2019 05:46 pm

    When updating via cvs, how dows one delete all the build directories? When I updated this afternoon, I did it manually, but there seem to be a few of them in different subdirectories..

    On my system, I keep the CVS directory separate from my SBBS install directory. That way, my SBBS directory is kept clean of all the CVS directories and build directory etc.. And when I get new .js files from CVS, I copy those over to the appropriate directory in my SBBS tree. I'm running my BBS on a Windows system though, where I download pre-built binaries, and perhaps it's easier to keep my SBBS directory clean that way..

    Nightfox

    ---
    þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
  • From Dan Clough@VERT to Apam on Friday, July 12, 2019 12:26:00
    Apam wrote to All <=-

    I'm probably missing something obvious, or theres something in
    the wiki I missed...

    When updating via cvs, how dows one delete all the build
    directories? When I updated this afternoon, I did it manually,
    but there seem to be a few of them in different subdirectories..

    I guess I could make a script to find all the
    clang.freebsd.amd64.* folders and delete them, but I wanted to
    check if there was a recommended way?

    Just run the "cleanall.sh" script located in /sbbs/src

    More info here: http://wiki.synchro.net/install:nix#clean_rebuild


    ... Daddy, what does "now formatting drive C:" mean?
    === MultiMail/Linux v0.52
    --- SBBSecho 3.07-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Apam on Friday, July 12, 2019 13:09:16
    Re: Cleaning the Source Tree
    By: Apam to All on Fri Jul 12 2019 05:46 pm

    Hi

    I'm probably missing something obvious, or theres something in the wiki I missed...

    When updating via cvs, how dows one delete all the build directories?

    Run src/cleanall.sh.

    When I
    updated this afternoon, I did it manually, but there seem to be a few of them in different subdirectories..

    I guess I could make a script to find all the clang.freebsd.amd64.* folders and delete them, but I wanted to check if there was a recommended way?

    cleanall.sh is the recommended way. It'll do a "smart clean" so it just deletes dependent files, not the output directories themselves.

    digital man

    Synchronet/BBS Terminology Definition #81:
    XOFF = Transmit Off (ASCII 19, Ctrl-S)
    Norco, CA WX: 91.8øF, 40.0% humidity, 5 mph ENE wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Apam@VERT/NOCTURN to Digital Man on Saturday, July 13, 2019 12:27:37
    Re: Cleaning the Source Tree
    By: Digital Man to Apam on Fri Jul 12 2019 01:09 pm

    cleanall.sh is the recommended way. It'll do a "smart clean" so it just deletes dependent files, not the output directories themselves.

    Ah ok. I did actually try that, but had to edit it to use gmake instead of make - I'm not sure if just changing make to gmake worked or not, I don't remember, I guess it would have. At anyrate I'll use that in the future and let you know if I have any troubles.

    Would it be useful to add something like, if uname = linux use make else use gmake to it? I imagine most people use Linux rather than FreeBSD/OpenBSD etc and those that use BSD can easily edit the file.

    Andrew

    ---
    þ Synchronet þ Nocturnal - nocturnal.hopto.org:2023
  • From Dan Clough@VERT/PALANT to Apam on Saturday, July 13, 2019 09:14:00
    Apam wrote to Digital Man <=-

    cleanall.sh is the recommended way. It'll do a "smart clean" so it just deletes dependent files, not the output directories themselves.

    Ah ok. I did actually try that, but had to edit it to use gmake
    instead of make - I'm not sure if just changing make to gmake
    worked or not, I don't remember, I guess it would have. At
    anyrate I'll use that in the future and let you know if I have
    any troubles.

    Would it be useful to add something like, if uname = linux use
    make else use gmake to it? I imagine most people use Linux rather
    than FreeBSD/OpenBSD etc and those that use BSD can easily edit
    the file.

    On my (Slackware) Linux, 'gmake' is a symbolic link to 'make',
    which makes it work fine.

    /usr/bin/# ln -sf make gmake

    The above command should fix you right up.


    ... Rehab is for quitters.
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
  • From Apam@VERT/NOCTURN to Dan Clough on Sunday, July 14, 2019 08:17:33
    Re: Re: Cleaning the Source Tree
    By: Dan Clough to Apam on Sat Jul 13 2019 09:14 am

    On my (Slackware) Linux, 'gmake' is a symbolic link to 'make',
    which makes it work fine.

    /usr/bin/# ln -sf make gmake

    The above command should fix you right up.

    On FreeBSD make is BSD make, and doing something like that would totally bork the ports system.

    Andrew

    ---
    þ Synchronet þ Nocturnal - nocturnal.hopto.org:2023