[JimShorts]

@dynmosaic wrote:

However, this may not be the desired solution. As we are not just interested in the existence of libntfs.a, but the dependency of the change of any of source files in the libntfs directory, any change at all, this includes all the .h and .c files.

I had thought all those libs were really just from some other source, included with WiiMC for convenience. And if you wanted to tinker with those libraries from within the WiiMC tree, couldn’t you just go inside and do normal development? Edit-make-make install-repeat.

At most I’d think you’d want to just upgrade those libraries from their original source upon occasion. But who knows if it’s an issue even. Upgrading just because there is a new version doesn’t always make sense. New features that WiiMC doesn’t even make use of wouldn’t add any value.

I don’t know, it seems to me the focus ought to be on WiiMC, not these irritating but unfortunately necessary support libraries…

[JimShorts]

@dynmosaic wrote:

puddles,

One more Q for you. Right now, when I go to libs, do a make, it will start to build for every library, does not matter whether there is any change or not. Is there a way to build only when there is a change? I guess one has to put in the right dependency. So what’s the best way of achieving this?

Once the build completes there is some library that was built, buried down in the tree. This is what gets installed. Just determine a file that has to get built and use that to conditionally do the build.

For example:
dir1:
if [ ! -f libntfs/lib/libntfs.a ] ; then
cd libntfs && $(COMMAND1) ;
fi

Another thing I’d like is a target to “make clean”, but there doesn’t seem to be one. The whole thing seemed to be kind of a hack just to get the required libraries to be present.

If one were to do it right…

1)I’d put all the intelligence inside each subdirectory in libs, so each would have its own Makefile instead of the top one.
2) The top one would just have a SUBDIRS definition, and would just use an iteration mechanism to go into each subdir and make a target
3) All Makefiles would support the targets all, install and clean. You can do make clean multiple times without it erroring out (that is, all “rm” commands include the “-f” flag so they don’t fail even if the file to delete isn’t there.
4) Doing a “make all” on the toplevel would just do “make all” inside each subdirectory. Same for make install and make clean.
4) The make install step must be done by the user manually. On windows it’s “sudo make install”. On linux it’d be “sudo -E make install”. Note the -E is just to preserve the environment variables, which are needed to know where the devkitPPC tree is.

But that all would take some time to accomplish. And the real goal was tinkering with wiiMC in the first place…

ETA: Actually having the Makefiles be in each subtree can’t really work, as the Makefile itself has to be generated by using the right configure command. We had a hack I came up with where if you had a file “makefile” next to “Makefile”, the make utility itself will pick the “makefile” first. Then that file can invoke Makefile with “make -f Makefile” commands. But this won’t go over well if the OS is case insensitive.

[JimShorts]

@dynmosaic wrote:

For build under windows, the same Makefile won’t work, since there is no sudo -E command.

Yeah, I called the build steps dir1, dir2, dir3, etc. just to avoid the problem you discovered. I had thought of using d_pcre (for example) but thought it was too much typing.

If you’re interested in it building under windows also, better to just add some intelligence in the makefile itself, and use a single makefile.

Just have some conditional code like this in the Makefile:

ifeq ($(shell uname), Linux)

SUDO_CMD=sudo -E

else

SUDO_CMD=sudo

endif



all:

@echo sudo command is $(SUDO_CMD)

[JimShorts]

@dynmosaic wrote:

That’s strange.

I have another way to get it to compile. Just add on the configure parameters

–build=powerpc-eabi-gnu

for the definition of COMMAND2. Attached is the modified Makefile. This way it doesn’t matter where features.h is, and I think the config.guess isn’t even used.

[JimShorts]

@dynmosaic wrote:

Any idea what I am doing wrong?

Yep, that’s the bizarre problem regarding the location of features.h I mentioned. Do this:

sudo ln -s sys/features.h /opt/devkitPro/devkitPPC/powerpc-eabi/include/features.h

I’m not sure how else to fix it, lots of config.guess scripts expect to be able to include features.h, not sys/features.h…

[JimShorts]

@Tantric wrote:

Let me know if there’s anything else that you think I can do. 🙂

Wow that was fast.

I updated my copy and tried the build, here are some notes:

libs/Makefile has (CR)’s on every end of line, and each line that starts in whitespace below the all: line needs to use a single TAB character instead of multiple spaces, “make” complains about missing separator. This sort of thing often happens when a cut-and-paste is used from a browser window. I attached Makefile.gz which should be correct.

The libs/ tree built without errors when I fixed the Makefile.

Following files ought to be chmod 755 (just for completeness)
libs/libiconv/libcharset/configure
source/mplayer/configure
source/mplayer/DOCS/xml/configure
source/mplayer/ffmpeg/configure
libs/liba52/autotools/missing
libs/libiconv/build-aux/missing
libs/libmpg123/build/missing
source/mplayer/ffmpeg/version.sh

I think the toplevel build will be ok now. It’s still building on my machine. If there are any errors I’ll edit this…

[JimShorts]

@mophead7117 wrote:

Hey guys, I am new to all of this and I am trying to get SMB to work. I’ve looked all around the forums and could not find much to help. I’m pretty sure I’m doing everything right but not positive. If anyone could direct me to a step by step process or tell me how to do it here that would be great.

I’ll take a stab at this…

Assuming you can launch WiiMC click on the gears for “Settings”, then go down and click on “Network”, click on “Add SMB Share”. Click on the various fields to bring up a keyboard to be able to enter data. If your SMB share has guest access you probably only have to enter the “Share Name” and “Share IP” address.

As an example, in my setup I could have
Display Name Mystuff
Share IP 192.168.0.54
Share Name puddles
Username
Password ………..

Both username and password are blank in my case.

If you save your SMB, you can go back up and it will appear in the list below “SD – Wii” and
“USB – XXX”.

Good luck

[JimShorts]

@puddles wrote:

3) Colors grossly oversaturated, especially too much red. Both jpg image viewer and video playback.

My bad, problem was on my end. My component -> vga adapter was horribly out of adjustment.

[JimShorts]

@Tantric wrote:

Re: the channel – did you try updating to the latest channel with the 1.5 installer?

Yep, that did it. I was trying to use the 1.4 channel installer with 1.1.0.

I manually installed the 1.5 channel installer in my apps directory (not available on homebrew browser at this moment) and that worked fine to install 1.1.0 on main channels menu.

Thanks!

[Author]

Posts