Opened 14 years ago
Closed 13 years ago
#28946 closed defect (fixed)
awesome build fails in generated_icons.dir
Reported by: | chris@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | generated_icons.dir icons | Cc: | jeff.pitman@…, ryandesign (Ryan Carsten Schmidt) |
Port: | awesome |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi
I have tried to drill down the problem, but I can't make it work alone. I would be thankful if someone could take a look into the attached logfile. I think it is a bug.
port install awesome +x11_xcb+universal Warning: port definitions are more than two weeks old, consider using selfupdate ---> Computing dependencies for awesome ---> Fetching awesome ---> Verifying checksum(s) for awesome ---> Extracting awesome ---> Applying patches to awesome ---> Configuring awesome ---> Building awesome Error: Target org.macports.build returned: shell command failed (see log for details) Log for awesome is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_awesome/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
Regards
Chris
Attachments (1)
Change History (11)
Changed 14 years ago by chris@…
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to milosh@… |
Please remember to use WikiFormatting.
The relevant error from the log seems to be:
make[3]: *** No rule to make target `themes/default/titlebar/close_normal.png', needed by `CMakeFiles/generated_icons'. Stop.
comment:3 Changed 14 years ago by duncan.rumbold@…
This can be worked around by adding this to patch-CMakeLists.txt.diff (found this by googling the problem...Can't remember whether I found this on a gentoo forum or on the Awesome bugs comments): (The problem should of course by solved upstream but I think it might have been already)
@@ -274,14 +274,15 @@ # {{{ Theme icons file(GLOB icon_sources RELATIVE ${SOURCE_DIR} ${SOURCE_DIR}/themes/*/titlebar/*.png) -set(ALL_ICONS ${icon_sources}) foreach(icon ${icon_sources}) # Copy all icons to the build dir to simplify the following code. # Source paths are interpreted relative to ${SOURCE_DIR}, target paths # relative to ${BUILD_DIR}. get_filename_component(icon_path ${icon} PATH) + get_filename_component(icon_name ${icon} NAME) file(COPY ${icon} DESTINATION ${icon_path}) + set(ALL_ICONS ${ALL_ICONS} "${icon_path}/${icon_name}") endforeach() macro(a_icon_convert match replacement input)
comment:4 Changed 14 years ago by duncan.rumbold@…
After having worked around the problem with above patch, I then ran into a problem whereby the link stage couldn't complete successfully. The problem was that libiconv wasn't being specified as a link parameter. I added '-liconv' to the LINK_FLAGS in the cmake file which managed to complete the build, but I don't know enough about cmake or macports build parameters to come up with a 'real' solution. P.S. apologies for not using an appropriate markup tag for the code above.
comment:5 follow-up: 6 Changed 14 years ago by chris@…
I try to install awesome 3.4.4 and the CMakeLists.txt looks different. Which version did you install?
comment:6 Changed 14 years ago by duncan.rumbold@…
Replying to chris@…:
I try to install awesome 3.4.4 and the CMakeLists.txt looks different. Which version did you install?
Sorry I forgot to mention that critical piece of information! I am using 3.4.9, which is the latest stable version at this time.
comment:7 Changed 13 years ago by jmroot (Joshua Root)
Owner: | changed from milosh@… to macports-tickets@… |
---|
Maintainer has retired. Did this end up being fixed in 3.4.10?
comment:8 follow-up: 9 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
Is this still a problem with 3.4.11?
comment:9 Changed 13 years ago by chris@…
Replying to ryandesign@…:
Is this still a problem with 3.4.11?
I just checked and it compiles fine now. I don't know if it will run also, because I never had the chance to figure out a configuration. If you know a good howto, pls. let me know.
comment:10 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
I'm afraid I don't know anything about using awesome.
awesome installation log