Archiver 0.1 - IRIX/IMD GUI for tar.

[jimmer]

What I find strange is that it gives you errors at all. There really isn;t anything spectacularly dicey going on in the Motif stuff. It's really very straight forward. Oh well, in my experience a nice clean reinstall every couple of years is generally a good thing

[foetz]

just took the 0.3 for a ride and it built fine with 7.4.4. however i had to remove a few linker flags because you seem to add a lot of libs that you don't even use. one of them i didn't have installed so i tried cutting that down ... without problems.

[vishnu]

just took the 0.3 for a ride and it built fine with 7.4.4. however i had to remove a few linker flags because you seem to add a lot of libs that you don't even use. one of them i didn't have installed so i tried cutting that down ... without problems.

With that in mind I tried the same thing with this script:

Code: Select all

#!/bin/sh

CC -I/usr/Motif-2.1/include -c -g -o App.o App.C
CC -I/usr/Motif-2.1/include -c -g -o Config.o Config.C
CC -I/usr/Motif-2.1/include -c -g -o Main.o Main.C
CC -I/usr/Motif-2.1/include -c -g -o UI.o UI.C
CC -I/usr/Motif-2.1/include -c -g -o UI_Dialog_Create.o UI_Dialog_Create.C
CC -I/usr/Motif-2.1/include -c -g -o UI_Dialog_Settings.o UI_Dialog_Settings.C
CC -I/usr/Motif-2.1/include -c -g -o Utils.o Utils.C
CC -o archiver *.o -lXm -lvk -lSgm -lXt -lX11

And as a result I get a completely different failure:

Code: Select all

Process 2235: Stopped on signal SIGSEGV: Segmentation violation (default) _XtCompileCallbackList(<stripped>) ["EventUtil.c":508, 0x0f6465a8]

W, as they say, TF.

[foetz]

i cleaned up the makefile leaving only what's actually needed. i further kept the warning 84 (not used for resolving any symbol) which was very useful in this case. i also added a separate part for debugging which can be un/commented as required and changed CXXC_OPTS to -O3.
there's a lot more that can be added to CXXC_OPTS but since this is a work in progress i kept it conservative.

[vishnu]

So Goetz, I'm assuming when you use the file -> open pulldown on your compiled version it doesn't crash? My system is obviously borked...

[foetz]

hmm actually i didn't try that one. i tried the settings window and the option printout.

[duck]

0.3 worked just fine out of the box for me, but it seems to expect tar to be gnu tar and not the sgi default which does not support the z flag.

[jimmer]

Morning All,

@duck - welcome to the party Yeah, it uses GNU tar for the moment. One of the things I have on my TODO list is to make Archiver tar 'agnostic'.

@foetz - thanks for seeing to the makefile. I just copied it from my 'template' with all the extra libs setup. Was going to clean it up for the proper release, which i now realise was a silly idea as it makes it harder for others to compile till then. Sorry

@vishnu - come on, bite the bullet, reinstall

Not sure what I'll be working on today. I guess I really need to get the heart of the matter: spawning the external application and getting stdin/out redirected without issues.

J.

[vishnu]

For what it's worth (not much), this is what I've got so far for subclassing VkSubProcess, I can instantiate an object of the derived class but the compiler's telling me it doesn't have a create() function, which according to the manpage it should have. Not helpful but here it is (note call to create() is commented out in main() ):

Code: Select all

#include <Vk/VkApp.h>
#include <Vk/VkSimpleWindow.h>
#include <Vk/VkSubProcess.h>
#include <Xm/Text.h>

// derived class
class myvkWindow : public VkSimpleWindow
{
public:
    myvkWindow(const char * name);
    ~myvkWindow(){}
    virtual const char * className();
    Widget scrolledText;
};

// dervived class
class myvkSubProcess : public VkSubProcess
{
public:
    myvkSubProcess();
    ~myvkSubProcess(){}
    virtual const char * className();
};

myvkWindow::myvkWindow(const char * name) : VkSimpleWindow(name)
{
    scrolledText =  XmCreateScrolledText (mainWindowWidget(),
                                          (char *) "scrolledtext",
                                          NULL, 0);
    addView(scrolledText);
}

const char* myvkWindow::className()
{
    return "myvkWindow";
}

myvkSubProcess::myvkSubProcess() : VkSubProcess()
{

}

const char* myvkSubProcess::className()
{
    return "myvkSubProcess";
}

int main (int argc, char * argv[])
{
    VkApp          *app = new VkApp((char *) "vkapp", &argc, argv);
    myvkWindow     *win = new myvkWindow("myvkWindow");
    myvkSubProcess *sub = new myvkSubProcess();
    // sub->create();
    win->show();
    app->run();
    return 0;
}

[vishnu]

Top notch jimmer, now we're getting somewhere! Gotta admit I've got a crapton of C++ books that I've never read and "Design Patterns" is one of them...

[jimmer]

Update. Archiver 0.4.

- large tarball bug squashed (hopefully) by making App::cb_cli_output() callback much simpler and thus return much faster.
- added a progress bar dialog for extraction.
- changed to foetz's Makefile

A bunch of UI bugs still remain, hope to deal with those in 0.5.

If you have time, please compile and play with this during the week. I wont be able to work much on Archiver till the weekend. Thanks.

J.

PS. Moderators, perhaps my previous post in this thread about VkSubProcess should be moved to the recent VkSubProcess thread?

[foetz]

perhaps my previous post in this thread about VkSubProcess should be moved to the recent VkSubProcess thread?

you mean this: viewtopic.php?f=15&t=16732323 ?

[jimmer]

Yesh

[duck]

So I'm wondering, jimmer, would you be open to collaborative hacking(mercurial / git repo) or is this project just for you? I can perfectly understand the latter

[jimmer]

@Duck - Sure, why not. The more the merrier. Archiver 0.4 is the current state of the code. Setup some source repository thing, upload 0.4 and have at it. Of course we'll still have to send Vishnu tarballs on tape every couple of months...

I do think it should be a system that we can use natively on IRIX. My inner sarcastic bastard says that would be SCCS or at best CVS. But I guess it might be possible to build IRIX binaries for GIT. Not sure Mercurial/Hg will build on IRIX, nor will darcs. Of course you're going to have to post instructions how to use your <insert favourite webbased source control system> from the command line. After all, these days nobody wants to have to use a javascript-enabled webbrowser to do anything on IRIX.

J