#378 Print summary of enabled features when building Fuse

[Alberto Garcia]

This is similar to [#376], but for Fuse.

Fuse is more complex to build so I might have overlooked something, and I certainly haven't tested all available settings (Wii, win32, ...).

[Fredrick Meunier]

Looks good to me at first glance. Maybe you could add the timer and compat routines being used?

checking which timer routines to use... native
checking which compatibility routines to use... unix

[Alberto Garcia]

Is it worth it? Those are things the user has no control of, and they don't have any effect on user-visible features, or do they?

[Fredrick Meunier]

If the intent is only to show a summary of user-selectable configure options I don't think so, but I think of those bits as code variations that may not be obvious.

No need to add them if you don't think it would be useful.

[Alberto Garcia]

The main reason why I want to print that is that I want to know what features I'm enabling when I build Fuse.

This is useful for distributors (I'm maintaining the Debian packages). With this it's easy to see if all the compilation flags and dependencies are in place, and therefore the packages that users get are not missing any feature.

Whether Fuse uses SDL_Delay(), Sleep() or usleep() is an implementation detail that is not useful for me, to be honest. I have no problem to add it if you think it's important. There's also other bits of information that we could add (and are more important in my opinion), such as the installation path ($prefix) or the ROMs directory. I just decided to have the most important things in my initial patch.

[Fredrick Meunier]

That's fine - I've no objection to you just including what you want.

[Sergio Baldoví]

Looks good to me. The windows UI don't need special features and the wii UI is broken. Here are some suggestions,

Alter the order to put Fuse options at the end. They seem to be more important and need less scroll:

libspectrum features
...
fuse options
...
Type 'make' to compile Fuse

I've also noted more wording than libspectrum for the status:

zlib support enabled: yes

instead of:

zlib support: yes

More words means more text to read, makes difficult checking at a glance.

Finally, are the parameter expansions a bashism? (too much tired to check it)
${LIBSPEC_HAVE_ZLIB:-no}

[Alberto Garcia]

Alter the order to put Fuse options at the end. They seem to be more important and need less scroll

Ok

Finally, are the parameter expansions a bashism? (too much tired to check it)

They're not

http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_02

[Sergio Baldoví]

Thanks, committed in [r5766].