Closed Bug 314412 Opened 19 years ago Closed 19 years ago

Building CCK extension module

Categories

(CCK Graveyard :: CCK-General, defect)

Product:
CCK Graveyard
Component:
CCK-General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: kinger, Assigned: benjamin)

Details

The Firefox CCK is now being built on the trunk in extensions/ckk. In my .mozconfig, I have: ac_add_options --enable-extensions=default,cck I build from the top, and all seems hunky dory. Start Firefox, CCK is in the Tools menu and runs. However, when I make updates (I'm working on patches for Michael Kaply), I go to build the module (cd extensions/cck) and there is no Makefile. The is none in extensions/either. I don't feel like buidling from the top just for a small change, and I'm not even sure it will be picked up. Am I missing something?
Are you using an objdir? Makefile.in exists in the source dir, Makefile lives on the objdir.
Oops, silly me! Not sure if this is the right place to ask but ... Should we keep CCK bugs in this BZ Product, which is dormant from the old Netscape CCK days, or should be set up a new component elsewhere (e.g. in Other Applications)?
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.