Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] CERO_TARGET for building on 3800 box?
Date: Fri, 13 Apr 2012 08:18:40 -0700	[thread overview]
Message-ID: <CAA93jw6V2T_PMN_0BHEWTsxF3YgqD+YJLXA4H6iHA0cokCwyRw@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YBWRHAUrygEd3S6U4+r5ENh+66ojvg-fCWTwgn_DAesuw@mail.gmail.com>

I really need to sit down with a couple developers trying to build
their own sources
and nail down this script. Ketan had submitted a few patches, I had a
few more, and I view this as a major bottleneck for pushing this stuff
out, that requires tweaking and deep knowledge...

So, I will argue that the best way to get a build of your own that
actually works is to contact me over irc in the #bufferbloat channel,
and we can work through the problems that come up.

In the case below, the script predates the wnd3800, and the wndr3800
is built automatically from the build, so use the wnd3700 version.

I really did want to get build_cero.sh to just work, in particular I'd
like to get it integrated with buildbot somehow.

But a little more exposure to the real world problems that come up
would help harden things more.

On Fri, Apr 13, 2012 at 7:40 AM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
> Hi,
>
> I'm trying to follow
> http://www.bufferbloat.net/projects/cerowrt/wiki/Building_CeroWrt_on_your_own_machine
> to build cerowrt on my box to be able test and to provide patches.
>
> For my WNDR3800, should I edit ~/.cero and change
> CERO_TARGET=wndr3700v2
> to:
> CERO_TARGET=wndr3800
>
> build_cero.sh init gets me: cp: cannot stat `env/config-wndr3800': No such
> file or directory
> Should I worry or change back to 3700v2 in .cero?
>
> Also, I noticed git://github.com/dtaht/cerofiles.git is replaced with
> git://github.com/dtaht/cerofiles-3-3.git on github.
> I am amending the commands and adding a step to ln -s cerofiles-3.3
> cerofiles, but should I expect it to be renamed to cerofiles in the future?
>
> Thanks,
> Maciej
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

  reply	other threads:[~2012-04-13 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 14:40 Maciej Soltysiak
2012-04-13 15:18 ` Dave Taht [this message]
2012-04-13 19:38   ` Ketan Kulkarni
2012-04-16 14:35     ` Maciej Soltysiak
2012-04-16 14:43       ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6V2T_PMN_0BHEWTsxF3YgqD+YJLXA4H6iHA0cokCwyRw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox