Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 34

Thread: Contributors needed for wl500g packages

  1. #16
    Join Date
    Jul 2004
    Location
    near Lyon @ France
    Posts
    195
    Quote Originally Posted by cthings
    Thanx JF,
    I'll do a good test this weekend and will then send you the .mk files for addiotion to the official CVS.
    Feel free to open a sourceforge account and I'll add you to the optware developpers community. You will then be able to maintain your pound optware and many others if you like

    JF

  2. #17

    Exclamation mysql package

    can we have a package for mysql extension which works on OLEG's firmware?

  3. #18
    Join Date
    Jul 2004
    Location
    near Lyon @ France
    Posts
    195
    Quote Originally Posted by digimic
    can we have a package for mysql extension which works on OLEG's firmware?
    see http://wl500g.info/showpost.php?p=14559&postcount=9

  4. #19
    Join Date
    Jun 2005
    Location
    Slovenia
    Posts
    736
    Why there are so many broken download links in the unslung CVS when I issue
    Code:
    make source
    for nslu2 target?

    Is the cause change to monotone or just nobody tracks the changes?
    Last edited by oleo; 12-12-2005 at 21:01.

  5. #20
    Join Date
    Apr 2004
    Location
    Adelaide, Australia
    Posts
    88
    It's just that no-one has time to track all the sources for all the packages. Once they are built and in the feeds, then it's up to individual package contributors (or users) to notice that there is a new version and update to it.

    BTW, we have re-arranged the optware makefile so that new packages by default attempt to be built for wl500g. This means that new packages may appear by magic without any intervention by JF or myself.

    In doing so, we worked out how to build a whole lot more wl500g packages. In particular, those who have been looking for MySQL might find a Christmas present in the feed ...

    http://ipkg.nslu2-linux.org/feeds/op...ross/unstable/

    -- Rod (nslu2-linux project lead, and Optware infrastructure developer)

  6. #21
    Join Date
    Jun 2005
    Location
    Slovenia
    Posts
    736
    I mean that old download sources are lagging in download directory of the build machine. There is no instrument to check if the file is available for download or not. This introduces a big problem for newcomers as a lot of packages are deleted with a new version. And this is not tracked by Makefile. Such packages should be tagged somehow in Makefile. Or erase the download dir from time to time to look for NEED_TO_BE_FIXED packages!

    ______________________________
    waiting for uclibc-stdlibc++
    Last edited by oleo; 23-12-2005 at 11:21.

  7. #22
    Join Date
    Apr 2004
    Location
    Adelaide, Australia
    Posts
    88

    Optware source code repository moved to svn.nslu2-linux.org

    We have moved the Optware source code repository from sourceforge.net to our new svn.nslu2-linux.org site.

    http://svn.nslu2-linux.org/svnroot/optware

    You can also browse the source with the nice Trac interface at:

    http://trac.nslu2-linux.org/optware

    If you are an Optware developer, you need an NSLU2-Linux SSL client certficate to write to the new repository. All sourceforge.net write access has been disabled. Contact me if you need a certificate.

    There is no change to the feed contents or location.

    -- Rod

  8. #23
    Please,need counsel:
    Shall I WL- 500G Deluxe V and interface ADSL ( 2 conductor ) and WL- 500G has interface WAN,how gear connector ADSL 6 PIN to the WAN 8 PIN connector.
    Thank you

  9. #24

    Would like to contribute

    Hello. I've got an Asus Wl500gp and a computer with openSuse 10.2.
    I use Olegs feed. I've downloaded everything, to compile the kernel.
    It works well !!!
    Can I contribute? (But I'm not using UNSLUNG but Olegs feed. Is this a problem?)
    Can I use Your advises to compile for Olegs feed or is it completely different?
    Am I far from compiling ipkg packages?

  10. #25
    Join Date
    Jun 2005
    Location
    Slovenia
    Posts
    736
    Follow instructions on Optware packages at www.nslu2-linux.org.
    If you are able to rebuild the whole oleg|wl500g|openwrt-brcm24 package feed on your machine, then
    you are right for the job and can contact us at #nslu2-linux IRC channel.
    Last edited by oleo; 24-06-2007 at 01:29.

  11. #26

    Compiling tinyproxy

    Hello,

    I've tried many time to compile additional optware packages for my wl500g but i can't generate the ipkg file.

    Here the result of:

    Code:
    make tinyproxy-ipk
    Code:
     /bin/sh ../libtool  --mode=install /usr/bin/install -c -s tinyproxy /home/manu/optware/builds/tinyproxy-1.6.3-ipk/opt/sbin/mipsel-linux-tinyproxy
    /usr/bin/install -c -s tinyproxy /home/manu/optware/builds/tinyproxy-1.6.3-ipk/opt/sbin/mipsel-linux-tinyproxy
    strip: Unable to recognise the format of the input file `/home/manu/optware/builds/tinyproxy-1.6.3-ipk/opt/sbin/mipsel-linux-tinyproxy'
    /usr/bin/install: strip failed
    make[4]: *** [install-sbinPROGRAMS] Erreur 1
    make[4]: quittant le répertoire « /home/manu/optware/builds/tinyproxy/src »
    make[3]: *** [install-am] Erreur 2
    make[3]: quittant le répertoire « /home/manu/optware/builds/tinyproxy/src »
    make[2]: *** [install-recursive] Erreur 1
    make[2]: quittant le répertoire « /home/manu/optware/builds/tinyproxy »
    make[1]: *** [install-strip] Erreur 2
    make[1]: quittant le répertoire « /home/manu/optware/builds/tinyproxy »
    make: *** [/home/manu/optware/builds/tinyproxy_1.6.3-1_mipsel.ipk] Erreur 2
    manu@debian:~/optware$

  12. #27
    Here is tinyproxy.mk : (sorry for the split but the post was too long)

    Code:
    ###########################################################
    #
    # tinyproxy
    #
    ###########################################################
    
    # You must replace "tinyproxy" and "TINYPROXY" with the lower case name and
    # upper case name of your new package.  Some places below will say
    # "Do not change this" - that does not include this global change,
    # which must always be done to ensure we have unique names.
    
    #
    # TINYPROXY_VERSION, TINYPROXY_SITE and TINYPROXY_SOURCE define
    # the upstream location of the source code for the package.
    # TINYPROXY_DIR is the directory which is created when the source
    # archive is unpacked.
    # TINYPROXY_UNZIP is the command used to unzip the source.
    # It is usually "zcat" (for .gz) or "bzcat" (for .bz2)
    #
    # You should change all these variables to suit your package.
    # Please make sure that you add a description, and that you
    # list all your packages' dependencies, seperated by commas.
    # 
    # If you list yourself as MAINTAINER, please give a valid email
    # address, and indicate your irc nick if it cannot be easily deduced
    # from your name or email address.  If you leave MAINTAINER set to
    # "NSLU2 Linux" other developers will feel free to edit.
    #
    TINYPROXY_SITE=http://$(SOURCEFORGE_MIRROR)/sourceforge/tinyproxy
    TINYPROXY_VERSION=1.6.3
    TINYPROXY_SOURCE=tinyproxy-$(TINYPROXY_VERSION).tar.gz
    TINYPROXY_DIR=tinyproxy-$(TINYPROXY_VERSION)
    TINYPROXY_UNZIP=zcat
    TINYPROXY_MAINTAINER=NSLU2 Linux <nslu2-linux@yahoogroups.com>
    TINYPROXY_DESCRIPTION=Describe tinyproxy here.
    TINYPROXY_SECTION=
    TINYPROXY_PRIORITY=optional
    TINYPROXY_DEPENDS=
    TINYPROXY_SUGGESTS=
    TINYPROXY_CONFLICTS=
    TINYPROXY_CONFIGURE_ENV=ac_cv_header_libintl_h=no
    
    #
    # TINYPROXY_IPK_VERSION should be incremented when the ipk changes.
    #
    TINYPROXY_IPK_VERSION=1
    
    #
    # TINYPROXY_CONFFILES should be a list of user-editable files
    TINYPROXY_CONFFILES=/opt/etc/tinyproxy.conf /opt/etc/init.d/SXXtinyproxy
    
    #
    # TINYPROXY_PATCHES should list any patches, in the the order in
    # which they should be applied to the source code.
    #
    #TINYPROXY_PATCHES=$(TINYPROXY_SOURCE_DIR)/configure.patch
    
    #
    # If the compilation of the package requires additional
    # compilation or linking flags, then list them here.
    #
    TINYPROXY_CPPFLAGS=
    TINYPROXY_LDFLAGS=
    
    #
    # TINYPROXY_BUILD_DIR is the directory in which the build is done.
    # TINYPROXY_SOURCE_DIR is the directory which holds all the
    # patches and ipkg control files.
    # TINYPROXY_IPK_DIR is the directory in which the ipk is built.
    # TINYPROXY_IPK is the name of the resulting ipk files.
    #
    # You should not change any of these variables.
    #
    TINYPROXY_BUILD_DIR=$(BUILD_DIR)/tinyproxy
    TINYPROXY_SOURCE_DIR=$(SOURCE_DIR)/tinyproxy
    TINYPROXY_IPK_DIR=$(BUILD_DIR)/tinyproxy-$(TINYPROXY_VERSION)-ipk
    TINYPROXY_IPK=$(BUILD_DIR)/tinyproxy_$(TINYPROXY_VERSION)-$(TINYPROXY_IPK_VERSION)_$(TARGET_ARCH).ipk
    
    .PHONY: tinyproxy-source tinyproxy-unpack tinyproxy tinyproxy-stage tinyproxy-ipk tinyproxy-clean tinyproxy-dirclean tinyproxy-check
    
    #
    # This is the dependency on the source code.  If the source is missing,
    # then it will be fetched from the site using wget.
    #
    $(DL_DIR)/$(TINYPROXY_SOURCE):
    	$(WGET) -P $(DL_DIR) $(TINYPROXY_SITE)/$(TINYPROXY_SOURCE) || \
    	$(WGET) -P $(DL_DIR) $(SOURCES_NLO_SITE)/$(TINYPROXY_SOURCE)
    
    #
    # The source code depends on it existing within the download directory.
    # This target will be called by the top level Makefile to download the
    # source code's archive (.tar.gz, .bz2, etc.)
    #
    tinyproxy-source: $(DL_DIR)/$(TINYPROXY_SOURCE) $(TINYPROXY_PATCHES)
    
    #
    # This target unpacks the source code in the build directory.
    # If the source archive is not .tar.gz or .tar.bz2, then you will need
    # to change the commands here.  Patches to the source code are also
    # applied in this target as required.
    #
    # This target also configures the build within the build directory.
    # Flags such as LDFLAGS and CPPFLAGS should be passed into configure
    # and NOT $(MAKE) below.  Passing it to configure causes configure to
    # correctly BUILD the Makefile with the right paths, where passing it
    # to Make causes it to override the default search paths of the compiler.
    #
    # If the compilation of the package requires other packages to be staged
    # first, then do that first (e.g. "$(MAKE) <bar>-stage <baz>-stage").
    #
    # If the package uses  GNU libtool, you should invoke $(PATCH_LIBTOOL) as
    # shown below to make various patches to it.
    #
    $(TINYPROXY_BUILD_DIR)/.configured: $(DL_DIR)/$(TINYPROXY_SOURCE) $(TINYPROXY_PATCHES) make/tinyproxy.mk
    	rm -rf $(BUILD_DIR)/$(TINYPROXY_DIR) $(TINYPROXY_BUILD_DIR)
    	$(TINYPROXY_UNZIP) $(DL_DIR)/$(TINYPROXY_SOURCE) | tar -C $(BUILD_DIR) -xvf -
    	if test -n "$(TINYPROXY_PATCHES)" ; \
    		then cat $(TINYPROXY_PATCHES) | \
    		patch -d $(BUILD_DIR)/$(TINYPROXY_DIR) -p0 ; \
    	fi
    	if test "$(BUILD_DIR)/$(TINYPROXY_DIR)" != "$(TINYPROXY_BUILD_DIR)" ; \
    		then mv $(BUILD_DIR)/$(TINYPROXY_DIR) $(TINYPROXY_BUILD_DIR) ; \
    	fi
    	(cd $(TINYPROXY_BUILD_DIR); \
    		$(TARGET_CONFIGURE_OPTS) \
    		$(TINYPROXY_CONFIGURE_ENV) \
    		CPPFLAGS="$(STAGING_CPPFLAGS) $(TINYPROXY_CPPFLAGS)" \
    		LDFLAGS="$(STAGING_LDFLAGS) $(TINYPROXY_LDFLAGS)" \
    		./configure \
    		--build=$(GNU_HOST_NAME) \
    		--host=$(GNU_TARGET_NAME) \
    		--target=$(GNU_TARGET_NAME) \
    		--prefix=/opt \
    		--disable-nls \
    		--disable-static \
    	)
    	$(PATCH_LIBTOOL) $(TINYPROXY_BUILD_DIR)/libtool
    	touch $@
    
    tinyproxy-unpack: $(TINYPROXY_BUILD_DIR)/.configured
    
    #
    # This builds the actual binary.
    #
    $(TINYPROXY_BUILD_DIR)/.built: $(TINYPROXY_BUILD_DIR)/.configured
    	rm -f $@
    	$(MAKE) -C $(TINYPROXY_BUILD_DIR)
    	touch $@
    
    #
    # This is the build convenience target.
    #
    tinyproxy: $(TINYPROXY_BUILD_DIR)/.built
    
    #
    # If you are building a library, then you need to stage it too.
    #
    $(TINYPROXY_BUILD_DIR)/.staged: $(TINYPROXY_BUILD_DIR)/.built
    	rm -f $@
    	$(MAKE) -C $(TINYPROXY_BUILD_DIR) DESTDIR=$(STAGING_DIR) install
    	touch $@
    
    tinyproxy-stage: $(TINYPROXY_BUILD_DIR)/.staged
    
    #
    # This rule creates a control file for ipkg.  It is no longer
    # necessary to create a seperate control file under sources/tinyproxy
    #
    $(TINYPROXY_IPK_DIR)/CONTROL/control:
    	@install -d $(@D)
    	@rm -f $@
    	@echo "Package: tinyproxy" >>$@
    	@echo "Architecture: $(TARGET_ARCH)" >>$@
    	@echo "Priority: $(TINYPROXY_PRIORITY)" >>$@
    	@echo "Section: $(TINYPROXY_SECTION)" >>$@
    	@echo "Version: $(TINYPROXY_VERSION)-$(TINYPROXY_IPK_VERSION)" >>$@
    	@echo "Maintainer: $(TINYPROXY_MAINTAINER)" >>$@
    	@echo "Source: $(TINYPROXY_SITE)/$(TINYPROXY_SOURCE)" >>$@
    	@echo "Description: $(TINYPROXY_DESCRIPTION)" >>$@
    	@echo "Depends: $(TINYPROXY_DEPENDS)" >>$@
    	@echo "Suggests: $(TINYPROXY_SUGGESTS)" >>$@
    	@echo "Conflicts: $(TINYPROXY_CONFLICTS)" >>$@
    
    #
    # This builds the IPK file.
    #
    # Binaries should be installed into $(TINYPROXY_IPK_DIR)/opt/sbin or $(TINYPROXY_IPK_DIR)/opt/bin
    # (use the location in a well-known Linux distro as a guide for choosing sbin or bin).
    # Libraries and include files should be installed into $(TINYPROXY_IPK_DIR)/opt/{lib,include}
    # Configuration files should be installed in $(TINYPROXY_IPK_DIR)/opt/etc/tinyproxy/...
    # Documentation files should be installed in $(TINYPROXY_IPK_DIR)/opt/doc/tinyproxy/...
    # Daemon startup scripts should be installed in $(TINYPROXY_IPK_DIR)/opt/etc/init.d/S??tinyproxy
    #
    # You may need to patch your application to make it use these locations.
    #
    $(TINYPROXY_IPK): $(TINYPROXY_BUILD_DIR)/.built
    	rm -rf $(TINYPROXY_IPK_DIR) $(BUILD_DIR)/tinyproxy_*_$(TARGET_ARCH).ipk
    	$(MAKE) -C $(TINYPROXY_BUILD_DIR) DESTDIR=$(TINYPROXY_IPK_DIR) install-strip
    	install -d $(TINYPROXY_IPK_DIR)/opt/etc/
    	install -m 644 $(TINYPROXY_SOURCE_DIR)/tinyproxy.conf $(TINYPROXY_IPK_DIR)/opt/etc/tinyproxy.conf
    	install -d $(TINYPROXY_IPK_DIR)/opt/etc/init.d
    	install -m 755 $(TINYPROXY_SOURCE_DIR)/rc.tinyproxy $(TINYPROXY_IPK_DIR)/opt/etc/init.d/SXXtinyproxy
    	sed -i -e '/^#!/aOPTWARE_TARGET=${OPTWARE_TARGET}' $(TINYPROXY_IPK_DIR)/opt/etc/init.d/SXXtinyproxy
    	$(MAKE) $(TINYPROXY_IPK_DIR)/CONTROL/control
    	install -m 755 $(TINYPROXY_SOURCE_DIR)/postinst $(TINYPROXY_IPK_DIR)/CONTROL/postinst
    	sed -i -e '/^#!/aOPTWARE_TARGET=${OPTWARE_TARGET}' $(TINYPROXY_IPK_DIR)/CONTROL/postinst
    	install -m 755 $(TINYPROXY_SOURCE_DIR)/prerm $(TINYPROXY_IPK_DIR)/CONTROL/prerm
    	sed -i -e '/^#!/aOPTWARE_TARGET=${OPTWARE_TARGET}' $(TINYPROXY_IPK_DIR)/CONTROL/prerm
    	echo $(TINYPROXY_CONFFILES) | sed -e 's/ /\n/g' > $(TINYPROXY_IPK_DIR)/CONTROL/conffiles
    	cd $(BUILD_DIR); $(IPKG_BUILD) $(TINYPROXY_IPK_DIR)
    
    #
    # This is called from the top level makefile to create the IPK file.
    #
    tinyproxy-ipk: $(TINYPROXY_IPK)
    
    #
    # This is called from the top level makefile to clean all of the built files.
    #
    tinyproxy-clean:
    	rm -f $(TINYPROXY_BUILD_DIR)/.built
    	-$(MAKE) -C $(TINYPROXY_BUILD_DIR) clean
    
    #
    # This is called from the top level makefile to clean all dynamically created
    # directories.
    #
    tinyproxy-dirclean:
    	rm -rf $(BUILD_DIR)/$(TINYPROXY_DIR) $(TINYPROXY_BUILD_DIR) $(TINYPROXY_IPK_DIR) $(TINYPROXY_IPK)
    #
    #
    # Some sanity check for the package.
    #
    tinyproxy-check: $(TINYPROXY_IPK)
    	perl scripts/optware-check-package.pl --target=$(OPTWARE_TARGET) $(TINYPROXY_IPK)

  13. #28
    Join Date
    Apr 2004
    Location
    Adelaide, Australia
    Posts
    88
    Use 'install' instead of 'install-strip', and then use ${STRIP} to strip the binary afterwards.

    -- Rod

  14. #29
    I've managed to make a few packages, and fixed a few errors in some other ones.

    new: sabnzbd.mk and py-yenc.mk
    fixed : py-elementtree.mk, py-cherrypy.mk and automake.mk

    What is easiest way to get them into the feed?

    btw the only thing I changed in py-elementtree and py-cherrypy is the staging part. There was none, but needed for sabnzbd.mk.
    Should the ipkg version be increased for that??

  15. #30
    Join Date
    Apr 2004
    Location
    Adelaide, Australia
    Posts
    88
    Quote Originally Posted by DrChair View Post
    I've managed to make a few packages, and fixed a few errors in some other ones.

    new: sabnzbd.mk and py-yenc.mk
    fixed : py-elementtree.mk, py-cherrypy.mk and automake.mk

    What is easiest way to get them into the feed?

    btw the only thing I changed in py-elementtree and py-cherrypy is the staging part. There was none, but needed for sabnzbd.mk.
    Should the ipkg version be increased for that??
    The easiest way is to follow the instructions at http://www.nslu2-linux.org/wiki/Optw...ckageToOptware, and then we'll be happy to give you write access to the repository.

    It is always a good idea to change the ipkg version for any change in the build.

    -- Rod

Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. Unslung/WL500g packages available for Oleg's firmware
    By rwhitby in forum WL-500g Custom Development
    Replies: 136
    Last Post: 24-04-2009, 16:54
  2. Replies: 2
    Last Post: 16-04-2005, 11:57
  3. Some packages I compiled
    By Jean-Fabrice in forum WL-500g Custom Development
    Replies: 7
    Last Post: 23-03-2005, 13:29
  4. Additional packages and Asus fw 1.8.1.9
    By Spot in forum WL-500g Q&A
    Replies: 16
    Last Post: 04-10-2004, 19:49
  5. Help needed for WL500g...
    By Meuchi in forum WL-500g Q&A
    Replies: 1
    Last Post: 03-09-2004, 17:06

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •