Skip to contentSkip to conversation

missing expat-dirclean target

Buildroot Cristian Ionescu-Idbohrn 2 participants 7 messages Jul 8, 2007

lore
Share & tools
lore
#0 lore raw
expat.mk +3 -0
Index: expat.mk
===================================================================
@@ -70,6 +70,9 @@
 	#rm -f $(STAGING_DIR)/usr/bin/xmlwf  $(TARGET_DIR)/usr/bin/xmlwf
 	-$(MAKE) -C $(EXPAT_DIR) clean
 
+expat-dirclean:
+	rm -rf $(EXPAT_DIR)
+
 #############################################################
 #
 # Toplevel Makefile options
Signature · 1 line
Cristian
#1 lore raw

expat.mk line 70

Quoted 6 lines · Cristian Ionescu-Idbohrn

Index: expat.mk
===================================================================

expat.mk +0 -0
@@ -70,6 +70,9 @@
 	#rm -f $(STAGING_DIR)/usr/bin/xmlwf  $(TARGET_DIR)/usr/bin/xmlwf

the clean target must wipe installed stuff from the staging-dir. Please fix this, too.

expat.mk line 78

Quoted 8 lines
expat.mk +3 -0
 	-$(MAKE) -C $(EXPAT_DIR) clean
 
+expat-dirclean:
+	rm -rf $(EXPAT_DIR)
+
 #############################################################
 #
 # Toplevel Makefile options

this package uses wrong installation pathes, please fix and test while you're at it (i don't use it):

                --includedir=/include \

is wrong, whould be /usr/include. Most of these pathes are not needed, just --prefix=/usr should be enough.

#2 lore raw
Quoted 10 lines · Bernhard Fischer

expat.mk line 70

Quoted 6 lines · Cristian Ionescu-Idbohrn

Index: expat.mk
===================================================================

expat.mk +0 -0
@@ -70,6 +70,9 @@
 	#rm -f $(STAGING_DIR)/usr/bin/xmlwf  $(TARGET_DIR)/usr/bin/xmlwf

the clean target must wipe installed stuff from the staging-dir. Please fix this, too.

Looks like stuff is removed both from STAGING_DIR and TARGET_DIR. Is this the correct behaviour?

Quoted 6 lines

this package uses wrong installation pathes, please fix and test while you're at it (i don't use it):

                --includedir=/include \

is wrong, whould be /usr/include. Most of these pathes are not needed, just --prefix=/usr should be enough.

Will do.

Signature · 1 line
Cristian
#3 lore raw
Quoted 13 lines · Cristian Ionescu-Idbohrn
Quoted 10 lines · Bernhard Fischer

expat.mk line 70

Quoted 6 lines · Cristian Ionescu-Idbohrn

Index: expat.mk
===================================================================

expat.mk +0 -0
@@ -70,6 +70,9 @@
 	#rm -f $(STAGING_DIR)/usr/bin/xmlwf  $(TARGET_DIR)/usr/bin/xmlwf

the clean target must wipe installed stuff from the staging-dir. Please fix this, too.

Quoted 2 lines

Looks like stuff is removed both from STAGING_DIR and TARGET_DIR. Is this the correct behaviour?

I think removing stuff from both staging_dir and target_dir is the way to go, yes.

Consider somebody intending to turn off a package. The usual intuitive way is IMHO to make foo-clean then reconfigure to remove that package.

I'm open to alternative suggestions, of course.

Quoted 8 lines
Quoted 6 lines

this package uses wrong installation pathes, please fix and test while you're at it (i don't use it):

                --includedir=/include \

is wrong, whould be /usr/include. Most of these pathes are not needed, just --prefix=/usr should be enough.

Will do.

thanks alot in advance!

#4 lore raw
Quoted 7 lines · Bernhard Fischer
Quoted 3 lines · Cristian Ionescu-Idbohrn

Looks like stuff is removed both from STAGING_DIR and TARGET_DIR. Is this the correct behaviour?

I think removing stuff from both staging_dir and target_dir is the way to go, yes.

Alright. I still wish every makefile had a target called called <something>-uninstall to do that.

Quoted 4 lines

Consider somebody intending to turn off a package. The usual intuitive way is IMHO to make foo-clean then reconfigure to remove that package.

I'm open to alternative suggestions, of course.

This is how I wish it was done (looks more intuitive to me):

<something>-clean does the usual 'make clean' stuff
<something>-dirclean wipes out the build directory
<something>-uninstall wipes whatever was installed

Signature · 1 line
Cristian
#5 lore raw
Quoted 16 lines · Cristian Ionescu-Idbohrn
Quoted 7 lines · Bernhard Fischer
Quoted 3 lines · Cristian Ionescu-Idbohrn

Looks like stuff is removed both from STAGING_DIR and TARGET_DIR. Is this the correct behaviour?

I think removing stuff from both staging_dir and target_dir is the way to go, yes.

Alright. I still wish every makefile had a target called called <something>-uninstall to do that.

Quoted 3 lines

Consider somebody intending to turn off a package. The usual intuitive way is IMHO to make foo-clean then reconfigure to remove that package.

Quoted 7 lines
Quoted 1 line

I'm open to alternative suggestions, of course.

This is how I wish it was done (looks more intuitive to me):

<something>-clean does the usual 'make clean' stuff
<something>-dirclean wipes out the build directory
<something>-uninstall wipes whatever was installed

sounds ok to me, i'll let others comment. Care to send a patch if noone objects withing a couple of days?

cheers,

#6 lore raw
In reply to Bernhard Fischer
Quoted 10 lines · Bernhard Fischer
Quoted 8 lines
Quoted 6 lines

this package uses wrong installation pathes, please fix and test while you're at it (i don't use it):

                --includedir=/include \

is wrong, whould be /usr/include. Most of these pathes are not needed, just --prefix=/usr should be enough.

Will do.

thanks alot in advance!

Done this too now.
Please have a look att the attached (broke some long lines too).

Signature · 8 lines
Cristian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ex.patch
Type: text/x-diff
Size: 1633 bytes
Desc: 
Url : http://busybox.net/lists/buildroot/attachments/20070708/7d362ac3/attachment-0001.bin